| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Catalog/Metadata consistency during changeset extraction from wal |
| Date: | 2012-06-21 15:05:04 |
| Message-ID: | CA+U5nM+hh6x2h9j+UJJkHYUQPo_dcg8aTQywzLAkL1p9LEppxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 June 2012 15:53, Andres Freund <andres(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-06-21 15:13:48 | Re: Catalog/Metadata consistency during changeset extraction from wal |
| Previous Message | Alex Hunsaker | 2012-06-21 14:59:37 | Re: pl/perl and utf-8 in sql_ascii databases |