| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Васильев Дмитрий <d(dot)vasilyev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Performance degradation in commit ac1d794 |
| Date: | 2016-01-14 17:10:15 |
| Message-ID: | 5943.1452791415@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Jan 14, 2016 at 12:06 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Do we want to provide a backward compatible API for all this? I'm fine
>> either way.
> How would that work?
I see no great need to be backwards-compatible on this, especially if it
would complicate matters at all. I doubt there's a lot of third-party
code using WaitLatch right now. Just make sure there's an obvious
compile failure for anyone who is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2016-01-14 17:13:35 | Re: SET syntax in INSERT |
| Previous Message | Robert Haas | 2016-01-14 17:07:23 | Re: Performance degradation in commit ac1d794 |