Re: Changeset Extraction v7.9.1
От | Robert Haas |
---|---|
Тема | Re: Changeset Extraction v7.9.1 |
Дата | |
Msg-id | CA+TgmoZRWt7aa8M3ZyV7bMcTQSY_oSg-bUDMO1mvQNXpGEMpCA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Changeset Extraction v7.9.1 (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-hackers |
On Mon, Mar 10, 2014 at 4:55 PM, Josh Berkus <josh@agliodbs.com> wrote: > On 03/10/2014 12:46 PM, Robert Haas wrote: >> On Mon, Mar 10, 2014 at 3:38 PM, Josh Berkus <josh@agliodbs.com> wrote: >>> On 03/10/2014 11:54 AM, Robert Haas wrote: >>>> I've committed this patch now with a few further tweaks, leaving this >>>> issue unaddressed. It may well be something that needs improvement, >>>> but I don't think it's a big enough issue to justify holding back a >>>> commit. >>> >>> Wait, does this mean Changesets is committed? Or only part of it? >> >> The core of the feature was b89e151054a05f0f6d356ca52e3b725dd0505e53, >> but that only allowed it through the SQL interface. The new commit, >> 8722017bbcbc95e311bbaa6d21cd028e296e5e35, makes it available via >> walsender interface. There isn't a client for that interface yet, but >> if you're wondering whether it's time to break out the champagne, I'm >> thinking probably. > > Yeah, that's my thoughts. Although I might wait for recvlogical. Will > put documentation wordsmithing on my todo list once Andres commits. Is this your way of announcing that Andres is getting a commit bit, or did you just mis-speak? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: