Re: BUG #15977: Inconsistent behavior in chained transactions - Mailing list pgsql-bugs

From fn ln
Subject Re: BUG #15977: Inconsistent behavior in chained transactions
Date
Msg-id CA+99BHoWDs19t4rLEeifNs4fNp4iHQD=na1TYGn+rpCTWvkMJg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15977: Inconsistent behavior in chained transactions  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: BUG #15977: Inconsistent behavior in chained transactions  (Fabien COELHO <coelho@cri.ensmp.fr>)
Re: BUG #15977: Inconsistent behavior in chained transactions  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-bugs
> The usual approach is to send self-contained and numbered patches,
> eg "chain-fix-1.patch", "chain-fix-2.patch", and so on, unless there are
> complex patches designed to be committed in stages.
Thanks, I got it. I have never made a patch before so I'll keep it in my mind.
Self-contained patch is now attached.

> it can be left blank
I'm fine with that.
Attachment

pgsql-bugs by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions
Next
From: PG Bug reporting form
Date:
Subject: BUG #15983: pg_dump converts CRLF to LF