[COMMITTERS] pgsql: Improve docs for timing and skipping of checkpoints
Improve docs for timing and skipping of checkpoints Greg Smith Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/43342891861cc2d08dea2b1c8b190e15e5a36551 Modified Files -- doc/src/sgml/wal.sgml | 11 +-- 1 files changed, 9 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Support range data types.
Support range data types. Selectivity estimation functions are missing for some range type operators, which is a TODO. Jeff Davis Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4429f6a9e3e12bb4af6e3677fbc78cd80f160252 Modified Files -- doc/src/sgml/catalogs.sgml | 77 + doc/src/sgml/datatype.sgml | 16 +- doc/src/sgml/extend.sgml | 22 +- doc/src/sgml/filelist.sgml |1 + doc/src/sgml/func.sgml | 304 +++ doc/src/sgml/plpgsql.sgml|6 +- doc/src/sgml/rangetypes.sgml | 373 doc/src/sgml/ref/create_type.sgml| 61 +- doc/src/sgml/xfunc.sgml |6 +- src/backend/catalog/Makefile |6 +- src/backend/catalog/pg_proc.c| 63 +- src/backend/catalog/pg_range.c | 136 ++ src/backend/commands/typecmds.c | 445 +- src/backend/executor/functions.c |1 + src/backend/nodes/copyfuncs.c| 14 + src/backend/nodes/equalfuncs.c | 12 + src/backend/parser/gram.y|7 + src/backend/parser/parse_coerce.c| 180 ++- src/backend/tcop/utility.c | 13 + src/backend/utils/adt/Makefile |4 +- src/backend/utils/adt/date.c |1 - src/backend/utils/adt/pseudotypes.c | 24 + src/backend/utils/adt/rangetypes.c | 2153 ++ src/backend/utils/adt/rangetypes_gist.c | 587 ++ src/backend/utils/cache/lsyscache.c | 30 + src/backend/utils/cache/syscache.c | 12 + src/backend/utils/fmgr/funcapi.c | 115 +- src/bin/pg_dump/pg_dump.c| 184 ++- src/include/catalog/catversion.h |3 +- src/include/catalog/indexing.h |3 + src/include/catalog/pg_amop.h| 30 + src/include/catalog/pg_amproc.h |9 + src/include/catalog/pg_opclass.h |3 + src/include/catalog/pg_operator.h| 39 + src/include/catalog/pg_opfamily.h|3 + src/include/catalog/pg_proc.h| 147 ++ src/include/catalog/pg_range.h | 84 + src/include/catalog/pg_type.h| 29 +- src/include/commands/typecmds.h |1 + src/include/nodes/nodes.h|1 + src/include/nodes/parsenodes.h | 11 + src/include/utils/lsyscache.h|2 + src/include/utils/rangetypes.h | 159 ++ src/include/utils/syscache.h |1 + src/pl/plpgsql/src/pl_comp.c | 10 +- src/test/regress/expected/collate.linux.utf8.out | 17 + src/test/regress/expected/opr_sanity.out | 37 +- src/test/regress/expected/plpgsql.out| 14 + src/test/regress/expected/rangetypes.out | 951 ++ src/test/regress/expected/sanity_check.out |3 +- src/test/regress/expected/type_sanity.out|2 +- src/test/regress/parallel_schedule |2 +- src/test/regress/serial_schedule |1 + src/test/regress/sql/collate.linux.utf8.sql | 11 + src/test/regress/sql/opr_sanity.sql | 12 +- src/test/regress/sql/plpgsql.sql | 10 + src/test/regress/sql/rangetypes.sql | 371 src/test/regress/sql/type_sanity.sql |2 +- 58 files changed, 6718 insertions(+), 103 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Pre-pad WAL files when streaming transaction log
Pre-pad WAL files when streaming transaction log Instead of filling files as they appear, pre-pad the WAL files received when streaming xlog the same way that the server does. Data is streamed into a .partial file which is then renamed()d into palce when it's complete, but it will always be 16MB. This also means that the starting position for pg_receivexlog is now simply right after the last complete segment, and we never need to deal with partial segments there. Patch by me, review by Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e7cc8437bbff99cbc7f07f852f5169ba1356a414 Modified Files -- src/bin/pg_basebackup/pg_receivexlog.c | 81 +++-- src/bin/pg_basebackup/receivelog.c | 123 +--- 2 files changed, 125 insertions(+), 79 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Properly close replication connection in pg_receivexlog
Properly close replication connection in pg_receivexlog Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/3b06105c7d999752177f98fdad20278d57804f8f Modified Files -- src/bin/pg_basebackup/pg_receivexlog.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Do not treat a superuser as a member of every role for HBA purpo
Do not treat a superuser as a member of every role for HBA purposes. This makes it possible to use reject lines with group roles. Andrew Dunstan, reviewd by Robert Haas. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/94cd0f1ad8af722a48a30a1087377b52ca99d633 Modified Files -- doc/src/sgml/client-auth.sgml |5 - src/backend/libpq/hba.c |9 +++-- 2 files changed, 11 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Implement a dry-run mode for isolationtester
Implement a dry-run mode for isolationtester This mode prints out the permutations that would be run by the given spec file, in the same format used by the permutation lines in spec files. This helps in building new spec files. Author: Alexander Shulgin, with some tweaks by me Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7ed36056751cc900418871b39595100cbb06de21 Modified Files -- src/test/isolation/isolationtester.c | 73 +- 1 files changed, 63 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Adjust pg_upgrade "new database skip" code, e.g. 'postgres', to
Adjust pg_upgrade "new database skip" code, e.g. 'postgres', to more cleanly handle old/new database mismatches. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/84b8fcaa923259d6f7daf228183ecbeb924dc950 Modified Files -- contrib/pg_upgrade/relfilenode.c | 20 +++- 1 files changed, 11 insertions(+), 9 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Do not treat a superuser as a member of every role for HBA purpo
Andrew Dunstan writes: > Do not treat a superuser as a member of every role for HBA purposes. > This makes it possible to use reject lines with group roles. As committed, this patch also changes the behavior of "samerole", but the doc update fails to reflect that. regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Do not treat a superuser as a member of every role for HBA purpo
On 11/03/2011 03:16 PM, Tom Lane wrote: Andrew Dunstan writes: Do not treat a superuser as a member of every role for HBA purposes. This makes it possible to use reject lines with group roles. As committed, this patch also changes the behavior of "samerole", but the doc update fails to reflect that. I'm happy to update the docs if you think it's necessary. I think this is desired behaviour, for the same reason as for named roles, namely that you can add superusers to the list if necessary. I can't think of a sane case where this would make a difference, but I'm happy to be pedantic if you like. cheers andrew -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Role membership of superusers is only by explicit membership for
Role membership of superusers is only by explicit membership for HBA. Document that this rule applies to 'samerole' as well as to named roles. Per gripe from Tom Lane. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f66c8252ab9a64dd49a0af2b481a2621dd008768 Modified Files -- doc/src/sgml/client-auth.sgml |4 1 files changed, 4 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix inline_set_returning_function() to allow multiple OUT parame
Fix inline_set_returning_function() to allow multiple OUT parameters. inline_set_returning_function failed to distinguish functions returning generic RECORD (which require a column list in the RTE, as well as run-time type checking) from those with multiple OUT parameters (which do not). This prevented inlining from happening. Per complaint from Jay Levitt. Back-patch to 8.4 where this capability was introduced. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/515e813543dad5464c1a226fd068fd4daf26a7f9 Modified Files -- src/backend/optimizer/util/clauses.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix inline_set_returning_function() to allow multiple OUT parame
Fix inline_set_returning_function() to allow multiple OUT parameters. inline_set_returning_function failed to distinguish functions returning generic RECORD (which require a column list in the RTE, as well as run-time type checking) from those with multiple OUT parameters (which do not). This prevented inlining from happening. Per complaint from Jay Levitt. Back-patch to 8.4 where this capability was introduced. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1819a375f117b8f98f6d4dd33bf53169e5e001ba Modified Files -- src/backend/optimizer/util/clauses.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix inline_set_returning_function() to allow multiple OUT parame
Fix inline_set_returning_function() to allow multiple OUT parameters. inline_set_returning_function failed to distinguish functions returning generic RECORD (which require a column list in the RTE, as well as run-time type checking) from those with multiple OUT parameters (which do not). This prevented inlining from happening. Per complaint from Jay Levitt. Back-patch to 8.4 where this capability was introduced. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9fc28fb5ea16c7f335aba052a2c31bbd03932f09 Modified Files -- src/backend/optimizer/util/clauses.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix inline_set_returning_function() to allow multiple OUT parame
Fix inline_set_returning_function() to allow multiple OUT parameters. inline_set_returning_function failed to distinguish functions returning generic RECORD (which require a column list in the RTE, as well as run-time type checking) from those with multiple OUT parameters (which do not). This prevented inlining from happening. Per complaint from Jay Levitt. Back-patch to 8.4 where this capability was introduced. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9b3c35a9db418379fc760105df04ac30810f9c88 Modified Files -- src/backend/optimizer/util/clauses.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus code in contrib/ tsearch dictionary examples.
Fix bogus code in contrib/ tsearch dictionary examples. Both dict_int and dict_xsyn were blithely assuming that whatever memory palloc gives back will be pre-zeroed. This would typically work for just about long enough to run their regression tests, and no longer :-(. The pre-9.0 code in dict_xsyn was even lamer than that, as it would happily give back a pointer to the result of palloc(0), encouraging its caller to access off the end of memory. Again, this would just barely fail to fail as long as memory contained nothing but zeroes. Per a report from Rodrigo Hjort that code based on these examples didn't work reliably. Branch -- REL8_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/0dddbbcd3178242f24d7476e12436ec7e1340f6d Modified Files -- contrib/dict_int/dict_int.c |2 +- contrib/dict_xsyn/dict_xsyn.c |8 +--- 2 files changed, 6 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus code in contrib/ tsearch dictionary examples.
Fix bogus code in contrib/ tsearch dictionary examples. Both dict_int and dict_xsyn were blithely assuming that whatever memory palloc gives back will be pre-zeroed. This would typically work for just about long enough to run their regression tests, and no longer :-(. The pre-9.0 code in dict_xsyn was even lamer than that, as it would happily give back a pointer to the result of palloc(0), encouraging its caller to access off the end of memory. Again, this would just barely fail to fail as long as memory contained nothing but zeroes. Per a report from Rodrigo Hjort that code based on these examples didn't work reliably. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/a4a5d40190ff2dfe2299d7b361a88db0dd5a4c82 Modified Files -- contrib/dict_int/dict_int.c |2 +- contrib/dict_xsyn/dict_xsyn.c |8 +--- 2 files changed, 6 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus code in contrib/ tsearch dictionary examples.
Fix bogus code in contrib/ tsearch dictionary examples. Both dict_int and dict_xsyn were blithely assuming that whatever memory palloc gives back will be pre-zeroed. This would typically work for just about long enough to run their regression tests, and no longer :-(. The pre-9.0 code in dict_xsyn was even lamer than that, as it would happily give back a pointer to the result of palloc(0), encouraging its caller to access off the end of memory. Again, this would just barely fail to fail as long as memory contained nothing but zeroes. Per a report from Rodrigo Hjort that code based on these examples didn't work reliably. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3fbfd40b37eaf2db8698df1b5e41bc0fd6c80b51 Modified Files -- contrib/dict_int/dict_int.c |2 +- contrib/dict_xsyn/dict_xsyn.c |2 ++ 2 files changed, 3 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Improve comments for TSLexeme data structure.
Improve comments for TSLexeme data structure. Mostly, clean up long-ago pgindent damage. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a0d2f05a0d433ab68ec378744ff920562a5ef681 Modified Files -- src/include/tsearch/ts_public.h | 27 +++ 1 files changed, 19 insertions(+), 8 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus code in contrib/ tsearch dictionary examples.
Fix bogus code in contrib/ tsearch dictionary examples. Both dict_int and dict_xsyn were blithely assuming that whatever memory palloc gives back will be pre-zeroed. This would typically work for just about long enough to run their regression tests, and no longer :-(. The pre-9.0 code in dict_xsyn was even lamer than that, as it would happily give back a pointer to the result of palloc(0), encouraging its caller to access off the end of memory. Again, this would just barely fail to fail as long as memory contained nothing but zeroes. Per a report from Rodrigo Hjort that code based on these examples didn't work reliably. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/92375ed2bdea82cd223244cf74dff532dc776405 Modified Files -- contrib/dict_int/dict_int.c |2 +- contrib/dict_xsyn/dict_xsyn.c |2 ++ 2 files changed, 3 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus code in contrib/ tsearch dictionary examples.
Fix bogus code in contrib/ tsearch dictionary examples. Both dict_int and dict_xsyn were blithely assuming that whatever memory palloc gives back will be pre-zeroed. This would typically work for just about long enough to run their regression tests, and no longer :-(. The pre-9.0 code in dict_xsyn was even lamer than that, as it would happily give back a pointer to the result of palloc(0), encouraging its caller to access off the end of memory. Again, this would just barely fail to fail as long as memory contained nothing but zeroes. Per a report from Rodrigo Hjort that code based on these examples didn't work reliably. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e3e3087d8717c26cd1c4581ba29274ac214eb816 Modified Files -- contrib/dict_int/dict_int.c |2 +- contrib/dict_xsyn/dict_xsyn.c |2 ++ 2 files changed, 3 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Unbreak isolationtester on Win32
Unbreak isolationtester on Win32 I broke it in a previous commit because I neglected to install the necessary incantations to have getopt() work on Windows. Per red blots in buildfarm. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e145891c984540a86788f88b604c766c934b17ea Modified Files -- src/test/isolation/isolationtester.c |9 + 1 files changed, 9 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
