Greg Williamson <gwilliamso...@yahoo.com> writes:
> We have a small database (few hundred megs of data, lass than half that in
> indexes) that suffers from index bloat. Currently we handle this with an
> hourly REINDEX command. This works but causes some small issues, so I have
> been expploring other methods.
> When I try to to drop constraints (typically UNIQUE) I sometimes get a crash
> of the psql client at the ALTER TABLE X DROP CONSTRAINT, and sometimes after
> I recreate the constraint at a commit. Transcript below:
> usher=# BEGIN;
> BEGIN
> gusher=# ALTER TABLE ourcodes DROP CONSTRAINT IF EXISTS ourcodes_pkey CASCADE;
> ALTER TABLE
> gusher=# ALTER TABLE ourcodes ADD CONSTRAINT ourcodes_pkey PRIMARY KEY (id);
> NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
> "ourcodes_pkey" for table "ourcodes"
> ALTER TABLE
> gusher=# COMMIT;
> FATAL: terminating connection due to administrator command
WTF? That should certainly not happen. Have you perhaps got a script
that runs around sending SIGTERM to backends that it thinks are blocking
something? Does anything show up in the postmaster log when this
happens?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
