From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: JSON decoding plugin |
Date: | 2013-12-10 15:17:59 |
Message-ID: | CAHyXU0yUyLKxMA8J4PuApw-UYV_fvXxTsodsUSYCOPA3W68qcA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 9, 2013 at 10:53 AM, Euler Taveira <euler(at)timbira(dot)com(dot)br> wrote:
> On 09-12-2013 13:12, Merlin Moncure wrote:
>> This is pretty neat. Couple minor questions:
>> *) Aren't you *en*coding data into json, not the other way around (decoding?)
>>
> Yes. The 'decoding' came from the functionality (logical decoding) and
> because the POC plugin is named 'test_decoding'. I also think that
> 'json_decoding' doesn't say much about the module purpose. I confess
> that I don't like the name but can't come up with a good name. Maybe
> 'wal2json' or 'logrep2json'? Could you suggest something?
I'm partial to wal2json actually.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-12-10 16:05:02 | Re: pg_archivecleanup bug |
Previous Message | Merlin Moncure | 2013-12-10 15:15:51 | Re: Compression of tables |