Discussion:
[ADMIN] Alter column varchar(n) via updating pg_attribute
(too old to reply)
Geoff Tolley
2011-09-01 22:41:48 UTC
Permalink
The last time this was asked about
(http://archives.postgresql.org/pgsql-admin/2010-02/msg00189.php), 9.0
was still alpha.

Is there any reason to suspect that direct pg_attribute manipulation to
expand a varchar(n) column might not play nice with streaming
replication/hot standby? (Naturally I'm also in the process of testing).

Thanks,
Geoff


---------------
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Tom Lane
2011-09-02 04:34:04 UTC
Permalink
Post by Geoff Tolley
The last time this was asked about
(http://archives.postgresql.org/pgsql-admin/2010-02/msg00189.php), 9.0
was still alpha.
Is there any reason to suspect that direct pg_attribute manipulation to
expand a varchar(n) column might not play nice with streaming
replication/hot standby? (Naturally I'm also in the process of testing).
I can't see why it wouldn't. The WAL/replication mechanism works at
such a low level that it has no idea whether an update to pg_attribute
originated in an official DDL command or a manual UPDATE of the catalog.
I think you should be more worried about fat-fingering the update than
whether it will be replicated correctly.

But, of course, testing is always a good idea ;-)

regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Loading...