Re: [COMMITTERS] pgsql: Move each SLRU's lwlocks to a separate tranche.

2016-03-25 Thread Andres Freund
On 2015-11-12 19:59:54 +, Robert Haas wrote: > Move each SLRU's lwlocks to a separate tranche. > > This makes it significantly easier to identify these lwlocks in > LWLOCK_STATS or Trace_lwlocks output. It's also arguably better > from a modularity standpoint, since lwlock.c no longer needs t

Re: [COMMITTERS] pgsql: Move each SLRU's lwlocks to a separate tranche.

2016-03-25 Thread Robert Haas
On Fri, Mar 25, 2016 at 3:05 AM, Andres Freund wrote: > On 2015-11-12 19:59:54 +, Robert Haas wrote: >> Move each SLRU's lwlocks to a separate tranche. >> >> This makes it significantly easier to identify these lwlocks in >> LWLOCK_STATS or Trace_lwlocks output. It's also arguably better >> f

Re: [COMMITTERS] pgsql: Move each SLRU's lwlocks to a separate tranche.

2016-03-25 Thread Andres Freund
On March 25, 2016 1:04:13 PM GMT+01:00, Robert Haas wrote: >On Fri, Mar 25, 2016 at 3:05 AM, Andres Freund >wrote: >> On 2015-11-12 19:59:54 +, Robert Haas wrote: >>> Move each SLRU's lwlocks to a separate tranche. >>> >>> This makes it significantly easier to identify these lwlocks in >>>

[COMMITTERS] pgsql: Don't split up SRFs when choosing to postpone SELECT output expr

2016-03-25 Thread Tom Lane
Don't split up SRFs when choosing to postpone SELECT output expressions. In commit 9118d03a8cca3d97 we taught the planner to postpone evaluation of set-returning functions in a SELECT's targetlist until after any sort done to satisfy ORDER BY. However, if we postpone some SRFs this way while othe

[COMMITTERS] pgsql: Fix DROP OPERATOR to reset oprcom/oprnegate links to the dropped

2016-03-25 Thread Tom Lane
Fix DROP OPERATOR to reset oprcom/oprnegate links to the dropped operator. This avoids leaving dangling links in pg_operator; which while fairly harmless are also unsightly. While we're at it, simplify OperatorUpd, which went through heap_modify_tuple for no very good reason considering it had al

[COMMITTERS] pgsql: In PL/Tcl, make database errors return additional info in the er

2016-03-25 Thread Tom Lane
In PL/Tcl, make database errors return additional info in the errorCode. Tcl has a convention for returning additional info about an error in a global variable named errorCode. Up to now PL/Tcl has ignored that, but this patch causes database errors caught by PL/Tcl to fill in errorCode with usef

[COMMITTERS] pgsql: Improve PL/Tcl errorCode facility by providing decoded name for

2016-03-25 Thread Tom Lane
Improve PL/Tcl errorCode facility by providing decoded name for SQLSTATE. We don't really want to encourage people to write numeric SQLSTATEs in programs; that's unreadable and error-prone. Copy plpgsql's infrastructure for converting between SQLSTATEs and exception names shown in Appendix A, and

[COMMITTERS] pgsql: Fix PL/Tcl for vpath builds.

2016-03-25 Thread Tom Lane
Fix PL/Tcl for vpath builds. Commit cd37bb78599dcf24 works for in-tree builds, but not so much for VPATH. Per buildfarm. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9f73a2f6d1c1305cf0dc749dbf631cffe26beda0 Modified Files -- src/pl/tcl/Makefile | 2 +

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2016c.

2016-03-25 Thread Tom Lane
Update time zone data files to tzdata release 2016c. DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions). Historical corrections for Lithuania, Moldova, Russia (Kaliningrad, Samara, Volgograd). As of 2015b, the keepers of the