| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Daniel Farina <daniel(at)heroku(dot)com> |
| Subject: | Re: Sync Rep v17 |
| Date: | 2011-03-02 17:39:09 |
| Message-ID: | AANLkTi=C22JUPUEo8EZHtvQW17BDRyWdS2wLp24M0UBT@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 2, 2011 at 9:58 AM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> To achieve the effect Fujii is looking for, we would have to silently drop
>> the connection. That would correctly leave the client not knowing whether
>> the transaction committed or not.
>
> +1
>
>>> It might be reasonable to COMMIT but also issue a warning message, or
>>> to just close the connection without telling the client what happened,
>>> but sending an error seems poor.
>>
>> Yeah, I guess that would work too, if the client knows to watch out for
>> those warnings.
>
> -1
yeah, unless by warning, you meant 'error'.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2011-03-02 17:40:18 | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |
| Previous Message | Tom Lane | 2011-03-02 17:35:22 | Re: Problem with composite type creation in C under Linux |