| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Istvan Soos <istvan(dot)soos(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to cleanup transaction after statement_timeout aborts a query? |
| Date: | 2024-09-08 14:18:32 |
| Message-ID: | 47b356914fd6ccfd828ffd62d00ff2bfce37f076.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2024-09-08 at 16:02 +0200, Istvan Soos wrote:
> On Sun, Sep 8, 2024 at 3:41 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> > You must be doing something wrong then, because it works:
>
> And you are right, I was doing something wrong:
>
> [...]
>
> I'm sorry for the noise.
No problem; I'm glad you could find the stumbling stone.
> Btw. Is there any guideline on how to write the client libraries or
> recommendations/tests that a client library should follow?
I'm afraid this question is too generic for an answer...
I'd say it should be easy and intuitive to use, and should be as robust
as possible (return meaningful error messages rather than crash).
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2024-09-08 17:45:39 | Re: Faster data load |
| Previous Message | Istvan Soos | 2024-09-08 14:02:34 | Re: How to cleanup transaction after statement_timeout aborts a query? |