Re: TODO-Item: B-tree fillfactor control

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO-Item: B-tree fillfactor control
Date: 2006-02-02 01:16:43
Message-ID: 43E15D7B.6020903@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> If you want it to be dumped by pg_dump (which is debatable IMHO) then
> it MUST NOT be a syntax extension, it has to be driven by a GUC
> variable, else we have compatibility problems with the dumps. We just
> went through this with WITH/WITHOUT OIDS.

Compatibility problems? CREATE INDEX isn't an SQL standard command is it?

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-02-02 01:59:37 Re: TODO-Item: B-tree fillfactor control
Previous Message Christopher Kings-Lynne 2006-02-02 01:15:59 8.1.3?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-02-02 01:59:37 Re: TODO-Item: B-tree fillfactor control
Previous Message Stephen Frost 2006-02-02 01:11:51 Re: pg_restore COPY error handling