Simon Riggs

Making PostgreSQL work for the most challenging solutions in the industry

[Simon Riggs @simon_riggs]

Things don't seemed to have calmed down at Fawlty Towers yet, but at least we got a decision that allows me to further simplify the code

[Simon Riggs @simon_riggs]

Tinkering with Hot Standby some more. Recent panic seems to have died down. Calm before the storm? We'll see

[Simon Riggs @simon_riggs]

@jtdavies Enjoy Venice - I'm not there until August now

[Simon Riggs @simon_riggs]

just got back from some very cool places - what next, I ponder?

[Simon Riggs @simon_riggs]

Squashing some more performance issues for a very smart team of guys. Seems there's always something that can be improved.

[Simon Riggs @simon_riggs]

Just about to take my kids on zip wire through the trees... time off is a wonderful thing.

[Simon Riggs @simon_riggs]

hmmm....still don't think the Postgres array facilities are complete. Annoying having to roll things together to make stuff work.

[Simon Riggs @simon_riggs]

Spending time with customers. It's always a good thing until they ask "So who's writing Postgres while you're here?". :-)

[Simon Riggs @simon_riggs]

Another fine day in the world of PostgreSQL closes in the UK, for me at least.

[Simon Riggs @simon_riggs]

Fighting with an SQL EXPLAIN and parameters

[Simon Riggs @simon_riggs]

Thinking about what people need in the next stage of PostgreSQL performance and high availability. What things are useful? What is too much?