Re: Catalog/Metadata consistency during changeset extraction from wal - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Catalog/Metadata consistency during changeset extraction from wal
Date
Msg-id CA+U5nM+hh6x2h9j+UJJkHYUQPo_dcg8aTQywzLAkL1p9LEppxQ@mail.gmail.com
Whole thread Raw
In response to Re: Catalog/Metadata consistency during changeset extraction from wal  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Catalog/Metadata consistency during changeset extraction from wal
List pgsql-hackers
On 21 June 2012 15:53, Andres Freund <andres@2ndquadrant.com> wrote:

>> ISTM we should maintain a lookup table on target system that has the
>> minimal required information on it.

> You need just about the whole catalog because the *_out procs might need to
> lookup types, operators and such again.
> Unless you want to rewrite those functions you need to provide a normal
> execution environment.

OK, so its more tables than I first thought, but its not all rows and
columns of all catalog tables.


> I don't see how your idea works because of that? Am I missing something?

Why does the number/size of the tables required make that not work?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: pl/perl and utf-8 in sql_ascii databases
Next
From: Andres Freund
Date:
Subject: Re: Catalog/Metadata consistency during changeset extraction from wal