[COMMITTERS] pgsql: Export a few more symbols required for test_shm_mq module.

2014-01-18 Thread Andrew Dunstan
Export a few more symbols required for test_shm_mq module. Patch from Amit Kapila. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7d7eee8bb702d7796a0d7c5886c1f4685f2e2806 Modified Files -- src/include/miscadmin.h |2 +- src/include/postmast

[COMMITTERS] pgsql: Make various variables const (read-only).

2014-01-18 Thread Tom Lane
Make various variables const (read-only). These changes should generally improve correctness/maintainability. A nice side benefit is that several kilobytes move from initialized data to text segment, allowing them to be shared across processes and probably reducing copy-on-write overhead while for

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Allow SET TABLESPACE to database default

2014-01-18 Thread Stephen Frost
Allow SET TABLESPACE to database default We've always allowed CREATE TABLE to create tables in the database's default tablespace without checking for CREATE permissions on that tablespace. Unfortunately, the original implementation of ALTER TABLE ... SET TABLESPACE didn't pick up on that exception

[COMMITTERS] pgsql: Add ALTER TABLESPACE ... MOVE command

2014-01-18 Thread Stephen Frost
Add ALTER TABLESPACE ... MOVE command This adds a 'MOVE' sub-command to ALTER TABLESPACE which allows moving sets of objects from one tablespace to another. This can be extremely handy and avoids a lot of error-prone scripting. ALTER TABLESPACE ... MOVE will only move objects the user owns, will

[COMMITTERS] pgsql: Fix VACUUM's reporting of dead-tuple counts to the stats collect

2014-01-18 Thread Tom Lane
Fix VACUUM's reporting of dead-tuple counts to the stats collector. Historically, VACUUM has just reported its new_rel_tuples estimate (the same thing it puts into pg_class.reltuples) to the stats collector. That number counts both live and dead-but-not-yet-reclaimable tuples. This behavior may on

[COMMITTERS] pgsql: Add CREATE TABLESPACE ... WITH ... Options

2014-01-18 Thread Stephen Frost
Add CREATE TABLESPACE ... WITH ... Options Tablespaces have a few options which can be set on them to give PG hints as to how the tablespace behaves (perhaps it's faster for sequential scans, or better able to handle random access, etc). These options were only available through the ALTER TABLESP