Horton

Re: Command Triggers, patch v11

Andres Freund <andres@anarazel.de>

View thread
From: "anarazel@anarazel.de" <andres@anarazel.de>
To: Thom Brown <thom@linux.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2012-03-03T00:39:13Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix SPGiST vacuum algorithm to handle concurrent tuple motion properly.

  2. Remove useless const qualifier

  3. Make executor's SELECT INTO code save and restore original tuple receiver.


"anarazel@anarazel.de" <andres@anarazel.de> schrieb:

>
>
>Thom Brown <thom@linux.com> schrieb:
>
>>On 2 March 2012 23:33, Thom Brown <thom@linux.com> wrote:
>>> On 2 March 2012 22:32, Dimitri Fontaine <dimitri@2ndquadrant.fr>
>>wrote:
>>>>>> test=# CREATE TABLE badname (id int, a int, b text);
>>>>>> ERROR:  invalid relation name: badname
>>>>>> test=# CREATE TABLE badname AS SELECT 1::int id, 1::int a,
>>''::text b;
>>>>>> SELECT 1
>>>>>>
>>>>>> This doesn't even get picked up by ANY COMMAND.
>>>>
>>>> I think Andres should add an entry for his patch on the commitfest.
>> Is
>>>> it ok?
>>>
>>> I'll try Andres' patch this weekend while I test yours.
>>
>>Actually no matter which patch I apply first, they cause the other to
>>fail to apply.
>I will try to fix that on the plain tomorrow (to NYC) but I am not yet
>sure when/where I will have internet access again.
One more try: To the list.

Andres

Please excuse the brevity and formatting - I am writing this on my mobile phone.