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 Haas||Date: 2009-12-19 01:55:33|
|Subject: Re: Largeobject Access Controls (r2460)|
|Previous:||From: Simon Riggs||Date: 2009-12-19 01:32:45|
|Subject: pgsql: Allow read only connections during recovery, known as Hot |