PostgreSQL Basics by Example

Re:PostgreSQL Basics by Example by mistermcgruff on Sunday August 18, 2013 @09:26PM (#6235091)

Repeat after me: set work_mem to 'XXXGB'; set maintenance_work_mem to 'YYYGB'; swing away!

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by rgbrenner on Sunday August 18, 2013 @09:52PM (#6235160)

work_mem is a per-sort setting. So if you have 20 users connected, running a single query with 4 sorts each, that's 80 x work_mem. If it's set to GB anything, that's going to get out of hand very fast.

I recommend this guide.. it's a good start: http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Serve...

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by wfn on Monday August 19, 2013 @05:47AM (#6236357)

More like, "set shared_buffers", "set effective_cache_size"..

Also, seconding rgbrenner re: "Tuning your PostgreSQL server" article.

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by kibibu on Sunday August 18, 2013 @09:35PM (#6235114)

This annoys me so much about PostgreSQL. Why not have useful defaults?!

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by ilikepi on Monday August 19, 2013 @12:56AM (#6235691)

The defaults are useful in that they reflect a configuration that is appropriate to get the system running on a large variety of hardware. It's not really the responsibility of the Pg developers to guess at the "best" settings for any specific environment, because environments and configurations vary greatly.

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by jedberg on Monday August 19, 2013 @02:20AM (#6235900)

I agree to a point, but it would be nice if there were some provided default configs for various classes of machines.

Especially defaults for the most popular EC2 instance types.

[ Parent | on HN ]

Re:PostgreSQL Basics by Example by VLM on Monday August 19, 2013 @10:39AM (#6237453)

Its two dimensional because of "various classes of applications"

[ Parent | on HN ]