Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> - Should indexes remember their fillfactors when they are created?
> >> The last fillfactors will be used on next reindex.
> 
> > They should remember, for sure, and REINDEX should use it.  It think
> > this is similar to the ALTER TABLE ALTER [ COLUMN ] ... SET STATISTICS 
> > functionality.  It will need to be dumped as well by pg_dump.
> 
> 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.

OK, so we are going to issue a GUC to set the fill factor in pg_dump,
but still have a fillfactor syntax for use by users?  That is how we do
WITH/WITHOUT OIDS.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

• Re: TODO-Item: B-tree fillfactor control at 2006-02-01 18:22:17 from Tom Lane

pgsql-hackers by date

Next:	From: Martijn van Oosterhout	Date: 2006-02-01 19:32:21
	Subject: Re: A note about testing EXEC_BACKEND on recent Linuxen
Previous:	From: Tom Lane	Date: 2006-02-01 18:22:17
	Subject: Re: TODO-Item: B-tree fillfactor control

pgsql-patches by date

Next:	From: Greg Sabino Mullane	Date: 2006-02-01 19:26:29
	Subject: Re: New pg_dump options: exclude tables/schemas, multiple
Previous:	From: Bruce Momjian	Date: 2006-02-01 18:30:43
	Subject: Re: New pg_dump options: exclude tables/schemas, multiple