| From: | fn ln <emuser20140816(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15977: Inconsistent behavior in chained transactions |
| Date: | 2019-08-29 13:55:47 |
| Message-ID: | CA+99BHoWDs19t4rLEeifNs4fNp4iHQD=na1TYGn+rpCTWvkMJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
> 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 | Content-Type | Size |
|---|---|---|
| disable_implicit_transaction_chaining-3.patch | application/octet-stream | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-08-29 14:07:36 | BUG #15983: pg_dump converts CRLF to LF |
| Previous Message | Fabien COELHO | 2019-08-29 13:01:11 | Re: BUG #15977: Inconsistent behavior in chained transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-29 14:00:54 | Re: RFC: seccomp-bpf support |
| Previous Message | Joe Conway | 2019-08-29 13:51:25 | Re: RFC: seccomp-bpf support |