On Sat, 2007-10-06 at 17:45 +0100, Dave Page wrote:
> CIC can't be run in a transaction block, so how do we queue up the
> drop & rename to run after it completes?
> Given the changes to VACUUM & CREATE DATABASE/TABLESPACE in 8.3 I
> would imagine it won't run in a multi-statement query either n
> --- Original Message ---
> From: Simon Riggs <[EMAIL PROTECTED]>
> To: Dave Page <[EMAIL PROTECTED]>
> Sent: 06/10/07, 08:33:30
> Subject: Re: [pgadmin-hackers] ALTER INDEX set fillfactor
>
> On Fri, 2007-10-05 at 21:24 +0100, Dave Page wrote:
> &g
On Fri, 2007-10-05 at 21:24 +0100, Dave Page wrote:
> Simon Riggs wrote:
> > It would be even better if there was an option to do that CONCURRENTLY,
> > i.e. add the new index and then drop the old one afterwards. (It's
> > unfortunate that there isn't a REINDEX concurrently, but there isn't
> > y
Simon Riggs wrote:
> pgadmin sneaks a REINDEX into the SQL when you specify a change to the
> fillfactor of an index.
>
> That's not very handy because the Postgres manual says specifically that
> ALTER INDEX doesn't issue a REINDEX. It's a perfectly valid thing to run
> on its own, since it will
pgadmin sneaks a REINDEX into the SQL when you specify a change to the
fillfactor of an index.
That's not very handy because the Postgres manual says specifically that
ALTER INDEX doesn't issue a REINDEX. It's a perfectly valid thing to run
on its own, since it will affect the future growth of th
