== PostgreSQL Weekly News - March 22 2015 ==
PGDay UK, Conference will be taking place on 7th July 2015 – it is aimed at
the UK PostgreSQL Community. The CfP is open until 13 April 2015.
http://www.postgresqlusergroup.org.uk
The Call For Papers for PostgresOpen 2015, being held in Dallas, Texas
from September 16th to 18th, is now open.
http://2015.postgresopen.org/callforpapers/
== PostgreSQL Product News ==
pgFormatter v1.3, a SQL formatter/beautifier which supports keywords
from SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011 and PostgreSQL
keywords are not in the standard, released.
http://sqlformat.darold.net/
pg_shard 1.1, an extension for scaling out PostgreSQL, released.
https://www.citusdata.com/blog/21-jason/139-announcing-pg-shard-1-1
== PostgreSQL Jobs for March ==
http://archives.postgresql.org/pgsql-jobs/2015-03/threads.php
== PostgreSQL Local ==
PGConf US 2015 takes place March 25-27, 2015 in NYC.
http://nyc.pgconf.us/2015/
The CfP for the second Swiss Postgres Conference, to be held June
25-26, 2015 at HSR Rapperswil, is open until April 1.
http://www.postgres-conference.ch/cfp/
The constituent assembly of the Swiss PostgreSQL
Users Group (SwissPUG) will be Friday, April 10, 2015
http://www.swisspug.org
India PostgreSQL UserGroup will hold a PGday in Bengaluru, Karnataka,
India on April 11, 2015. RSVP at
http://www.meetup.com/India-PUG/events/220553997/
There is a Postgres track in a database technology conference(DTCC) in
April 18, 2015 in Beijing, China.
http://dtcc.it168.com/list_jiabin.html
pgDay Paris will be held in Paris France on April 21, 2015.
http://pgday.paris/
PGCon 2015 is June 16-20 in Ottawa, Canada.
http://www.pgcon.org/2015/
== PostgreSQL in the News ==
Planet PostgreSQL: http://planet.postgresql.org/
PostgreSQL Weekly News is brought to you this week by David Fetter
Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to da...@fetter.org, German language
to p...@pgug.de, Italian language to p...@itpug.org. Spanish language
to p...@arpug.com.ar.
== Applied Patches ==
Tom Lane pushed:
- Replace insertion sort in contrib/intarray with qsort(). It's all
very well to claim that a simplistic sort is fast in easy cases, but
O(N^2) in the worst case is not good ... especially if the worst
case is as easy to hit as "descending order input". Replace that
bit with our standard qsort. Per bug #12866 from Maksym Boguk.
Back-patch to all active branches.
http://git.postgresql.org/pg/commitdiff/8d1f239003d0245dda636dfa6cf0add13bee69d6
- Allow foreign tables to participate in inheritance. Foreign tables
can now be inheritance children, or parents. Much of the system was
already ready for this, but we had to fix a few things of course,
mostly in the area of planner and executor handling of row locks.
As side effects of this, allow foreign tables to have NOT VALID
CHECK constraints (and hence to accept ALTER ... VALIDATE
CONSTRAINT), and to accept ALTER SET STORAGE and ALTER SET
WITH/WITHOUT OIDS. Continuing to disallow these things would've
required bizarre and inconsistent special cases in inheritance
behavior. Since foreign tables don't enforce CHECK constraints
anyway, a NOT VALID one is a complete no-op, but that doesn't mean
we shouldn't allow it. And it's possible that some FDWs might have
use for SET STORAGE or SET WITH OIDS, though doubtless they will be
no-ops for most. An additional change in support of this is that
when a ModifyTable node has multiple target tables, they will all
now be explicitly identified in EXPLAIN output, for example:
Update on pt1 (cost=0.00..321.05 rows=3541 width=46)
Update on pt1
Foreign Update on ft1
Foreign Update on ft2
Update on child3
-> Seq Scan on pt1 (cost=0.00..0.00 rows=1 width=46)
-> Foreign Scan on ft1 (cost=100.00..148.03 rows=1170 width=46)
-> Foreign Scan on ft2 (cost=100.00..148.03 rows=1170 width=46)
-> Seq Scan on child3 (cost=0.00..25.00 rows=1200 width=46)
This was done mainly to provide an unambiguous place to attach
"Remote SQL" fields, but it is useful for inherited updates even
when no foreign tables are involved. Shigeru Hanada and Etsuro
Fujita, reviewed by Ashutosh Bapat and Kyotaro Horiguchi, some
additional hacking by me
http://git.postgresql.org/pg/commitdiff/cb1ca4d800621dcae67ca6c799006de99fa4f0a5
Álvaro Herrera pushed:
- Fix out-of-array-bounds compiler warning. Since the array length
check is using a post-increment operator, the compiler complains
that there's a potential write to one element beyond the end of the
array. This is not possible currently: the only path to this
function is through pg_get_object_address(), which already verifies
that the input array is no more than two elements in length. Still,
a bug is a bug. No idea why my compiler doesn't complain about this
... Pointed out by Dead Rasheed and Peter Eisentraut
http:
