Skip site navigation (1) Skip section navigation (2)

Re: Removing pg_migrator limitations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: Removing pg_migrator limitations
Date: 2009-12-19 01:39:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Joe Conway <mail(at)joeconway(dot)com> writes:
> I like this approach overall, but wonder if it would be better to do:
> 	select pg_migrator_set_next_oid('table', 123456);
> 	select pg_migrator_set_next_oid('type', 12347);
> 	select pg_migrator_set_next_oid('toast_table', 123458);
> etc. Later we could easily add other supported objects...

Yeah, Bruce was just suggesting the same.  I do like that part of what
he mentioned, just because it'll be fewer special functions to add and
drop in pg_migrator.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-12-19 01:55:33
Subject: Re: Largeobject Access Controls (r2460)
Previous:From: Simon RiggsDate: 2009-12-19 01:32:45
Subject: pgsql: Allow read only connections during recovery, known as Hot

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group