| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Creating a DSA area to provide work space for parallel execution |
| Date: | 2016-12-16 21:27:36 |
| Message-ID: | 20161216212736.xc3kxqryuhoszrhp@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> I am not sure the issue was time so much as the ability to foresee all
> the problems we'd want to solve.
I think all that movement is okay. It's not like we're breaking things
to no purpose. The amount of effort that has to go into making
extensions compile with changed APIs is not *that* bad, surely; it's
pretty clear that we need to keep moving forward. All the changes you
listed that required lwlock changed have clearly been worth the
breakage, IMO.
> I think it's quite surprising how fast the LWLock system has evolved
> over the last few years. When I first started working on PostgreSQL
> in 2008, there was no LWLockAcquireOrWait, none of the Var stuff, the
> padding was much less sophisticated, no tranches, no atomics, volatile
> qualifiers all over the place... and all of that has changed in the
> last 5 years. Pretty amazing, actually, IMHO.
Yes, I agree.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-12-16 22:29:57 | Re: Proposal for changes to recovery.conf API |
| Previous Message | Robert Haas | 2016-12-16 20:54:22 | Re: Creating a DSA area to provide work space for parallel execution |