| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical Replication WIP |
| Date: | 2016-11-13 09:21:40 |
| Message-ID: | 20161113092140.c5kwjnc4vxgd35i4@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-11-13 00:40:12 -0500, Peter Eisentraut wrote:
> On 11/12/16 2:18 PM, Andres Freund wrote:
> >>> I also wonder if we want an easier to
> >>> > > extend form of pubinsert/update/delete (say to add pubddl, pubtruncate,
> >>> > > pub ... without changing the schema).
> >>> > >
> >> >
> >> > So like, text array that's then parsed everywhere (I am not doing
> >> > bitmask/int definitely)?
> > Yes, that sounds good to me. Then convert it to individual booleans or a
> > bitmask when loading the publications into the in-memory form (which you
> > already do).
>
> I'm not sure why that would be better. Adding catalog columns in future
> versions is not a problem.
It can be extended from what core provides, for extended versions of
replication solutions, for one. I presume publications/subscriptions
aren't only going to be used by built-in code.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-11-13 09:54:28 | Re: Do we need use more meaningful variables to replace 0 in catalog head files? |
| Previous Message | Andres Freund | 2016-11-13 09:20:06 | Re: Do we need use more meaningful variables to replace 0 in catalog head files? |