postgresql when it's not your job


“PostgreSQL When It’s Not Your Job” at DjangoCon US

4 September 2012

I presented “PostgreSQL When It’s Not Your Job” at DjangoCon US 2012, and you can get the slides here.

gudbergur at 17:38, 4 September 2012:

Thanks for the talk Christophe, it was really great!

Catalin Iacob at 13:30, 7 September 2012:

Hi Christophe,

Any chance of posting the slides for your EuroPython 2012 talk and training? I was there and have some notes but the slides would be very useful, especially since the video is not available for neither the talk nor the training.

Thanks for sharing your great expertise!

Jon Jensen at 11:01, 11 September 2012:

I wasn’t at the talk, but just read through the slides. Very nicely covers the space and seemed appropriate for the audience.

On logging & system resources: On really busy servers I have seen syslog or local file logging bog down the server I/O, but then sending to a nearby standalone syslog server usually solves that problem easily.

I initially wanted to object that running Bucardo or Slony doesn’t need an experienced DBA, but I think you’re probably right after all. :)

jerrico at 11:10, 11 September 2012:

Thanks for the presentation that I genuinely enjoyed at DjangoCon. During your session you mentioned a utility\solution that could be used to help with the issue with Django and Postgres. I thought it was in your slides but I can’t seem to find it there. Would you mind refreshing my memory? Thanks!

Xof at 11:35, 11 September 2012:

I was probably referring to the xact decorator: It’s available on Github. Thanks!

G Sando at 13:40, 19 September 2012:

There are some % of RAM mentioned on slide Resource Configure. Is it for case when server host database only or database + app?

Xof at 21:38, 19 September 2012:

That percentage is if the PG server is the only (significant) service on the box. If you are running other applications, you should reduce the RAM proportionately. But you shouldn’t be running other things on the server, anyway.