From: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
---|---|
To: | |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Two proposed modifications to the PostgreSQL FDW |
Date: | 2018-08-20 17:14:10 |
Message-ID: | CAN-RpxB_S5GUtBejhXYdT=hBg0W5GzvHNuJHAxFZ49nVqs-QLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
For the record, here's the proof of concept code for the transaction
manager which works off libpq connections.
It is not ready yet by any means. But it is included for design
discussion. If the previous patch gets in instead, that's fine, but figure
it is worth including here for discussion purposes.
Two things which are currently missing are a) an ability to specify in the
log file where the cleanup routine is located for a background worker and
b) a separation of backend responsibility for restarting cleanup efforts on
server start.
>
>>
>>
>
> --
> Best Regards,
> Chris Travers
> Head of Database
>
> Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
> Saarbrücker Straße 37a, 10405 Berlin
>
>
--
Best Regards,
Chris Travers
Head of Database
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
Attachment | Content-Type | Size |
---|---|---|
twophasecommit.h | application/octet-stream | 2.0 KB |
twophasecommit.c | application/octet-stream | 14.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Wu Ivy | 2018-08-20 17:27:36 | Re: Getting NOT NULL constraint from pg_attribute |
Previous Message | Andrew Gierth | 2018-08-20 16:58:49 | Re: A really subtle lexer bug |