Re: Proposed adjustments in MaxTupleSize andtoastthresholds

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>, "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
Subject: Re: Proposed adjustments in MaxTupleSize andtoastthresholds
Date: 2007-02-05 17:34:37
Message-ID: 1170696877.3645.424.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2007-02-05 at 11:52 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > Sounds like a good time to suggest making these values configurable,
> > within certain reasonable bounds to avoid bad behaviour.
>
> Actually, given what we've just learned --- namely that choosing these
> values at random is a bad idea --- I'd want to see a whole lot of
> positive evidence before adding such a configuration knob.

Sure. My understanding of the process we'd like to follow on this sort
of thing is:

1. make proposal, test for unseen negative effects or basic rejections
2. code performance prototype
3. assemble performance evidence
4. debate utility
5. complete coding
6. further review

Step 3 is always there for performance work, so even if you don't
mention it, I'll assume everybody wants to see that as soon as possible
before we progress.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-02-05 17:42:00 Re: VC2005 build and pthreads
Previous Message Simon Riggs 2007-02-05 17:26:01 Re: [previously on HACKERS] "Compacting" a relation