Re: Alter column varchar(n) via updating pg_attribute - Mailing list pgsql-admin

From Tom Lane
Subject Re: Alter column varchar(n) via updating pg_attribute
Date
Msg-id 4444.1314938044@sss.pgh.pa.us
Whole thread Raw
In response to Alter column varchar(n) via updating pg_attribute  (Geoff Tolley <geoff.tolley@yougov.com>)
List pgsql-admin
Geoff Tolley <geoff.tolley@yougov.com> writes:
> 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

pgsql-admin by date:

Previous
From: Geoff Tolley
Date:
Subject: Alter column varchar(n) via updating pg_attribute
Next
From: Rural Hunter
Date:
Subject: Re: plsql gets "out of memory"