| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical changeset generation v6.2 |
| Date: | 2013-10-15 13:47:08 |
| Message-ID: | 20131015134707.GJ5300@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-10-15 15:17:58 +0200, Andres Freund wrote:
> If we go for CSV I think we should put the entire primary key as one
> column (containing all the columns) and the entire row another.
What about columns like:
* action B|I|U|D|C
* xid
* timestamp
* tablename
* key name
* key column names
* key column types
* new key column values
* column names
* column types
* column values
* candidate_key_changed?
* old key column values
And have output plugin options
* include-column-types
* include-column-names
* include-primary-key
If something isn't included it's simply left out.
What still need to be determined is:
* how do we separate and escape multiple values in one CSV column
* how do we represent NULLs
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-15 13:47:31 | Re: Triggers on foreign tables |
| Previous Message | Andres Freund | 2013-10-15 13:29:30 | Re: logical changeset generation v6.2 |