| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical changeset generation v6.2 |
| Date: | 2013-10-15 15:14:11 |
| Message-ID: | 20131015151411.GR26805@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 15, 2013 at 11:02:39AM -0400, Robert Haas wrote:
> >> goals may be in conflict; we'll have to pick something.
> >
> > Note that parsing COPYs is a major PITA from most languages...
> >
> > Perhaps we should make the default output json instead? With every
> > action terminated by a nullbyte?
> > That's probably easier to parse from various scripting languages than
> > anything else.
>
> I could go for that. It's not quite as compact as I might hope, but
> JSON does seem to make people awfully happy.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Feeding such a JSON stream into a compression algorithm like lz4 or
snappy should result in a pretty compact stream. The latest lz4 updates
also have ability to use a pre-existing dictionary which would really
help remove the redundant pieces.
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-10-15 15:16:08 | Re: logical changeset generation v6.2 |
| Previous Message | Andres Freund | 2013-10-15 15:13:23 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |