Re: Alter column varchar(n) via updating pg_attribute

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Geoff Tolley <geoff(dot)tolley(at)yougov(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Alter column varchar(n) via updating pg_attribute
Date: 2011-09-02 04:34:04
Message-ID: 4444.1314938044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Geoff Tolley <geoff(dot)tolley(at)yougov(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rural Hunter 2011-09-03 03:30:26 Re: plsql gets "out of memory"
Previous Message Geoff Tolley 2011-09-01 22:41:48 Alter column varchar(n) via updating pg_attribute