Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#221 closed task (fixed)

Upgrade performance tips in documentation

Reported by: pramsey Owned by: jlivni
Priority: medium Milestone: PostGIS 1.5.0
Component: postgis Version: trunk
Keywords: Cc:

Description

Pull some of the advice from here http://2007.foss4g.org/presentations/view.php?abstract_id=117 into the documentation section on performance.

Attachments (1)

performance_tips.patch (4.5 KB) - added by jlivni 8 years ago.

Download all attachments as: .zip

Change History (5)

Changed 8 years ago by jlivni

Attachment: performance_tips.patch added

comment:1 Changed 8 years ago by jlivni

Status: newassigned

A small patch is attached, which includes a few of the tips/tweaks from the abstract.

comment:2 Changed 8 years ago by robe

Resolution: fixed
Status: assignedclosed

committed at r4425. Also took some artistic liberties by linking back to relevant sections of the PostgreSQL manual and other sources as well as items that are obsolete or have changed in later versions of PostgreSQL.

Kevin can you correct if I got anything wrong with the WAL part. That was the part I was most unsure about.

comment:3 Changed 8 years ago by robe

Patched for doc 1.4 at r4426

comment:4 Changed 8 years ago by kneufeld

Ah interesting. K, so these tips are getting quite old ... at the time of writing, was geared for 8.0 - 8.1 databases.

I think it would be better to rework the opening paragraphs ... just explain why someone would want to tune their databases. I'm definitely not after any publicity - remove references to me and the now obsolete doc. Perhaps a line "for further reading, see:" followed by a list of reference material like the PostgreSQL docs, Greg's notes, and any other current references folks find useful.

So, with that, the "this setting is now obsolete" type of comments could be replaced with just the current recommended settings as you have started to do, Regina. ie. checkpoint_segment_size and constraint_exclusion.

I can tackle this at some point.

Note: See TracTickets for help on using tickets.