Have CREATE TABLE LIKE add OID column if any LIKEd table has one
Also, process constraints for LIKEd tables at the end so an OID column
can be referenced in a constraint.
Report by Tom Lane
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b943f502b788a3708ca660785fd1
to_number(): allow 'V' to divide by 10^(the number of digits)
to_char('V') already multiplied in a similar manner.
Report by Jeremy Lowery
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/28b3a3d41a8b72841a3f5067217f639a7d337c0e
Modified Files
--
doc/sr
psql: allow \pset C in setting the title, matches \C
Report by David G. Johnston
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2145a766044b4de32ab154a074ade0bf78d021df
Modified Files
--
doc/src/sgml/ref/psql-ref.sgml |2 +-
src/bin/psql/command.c
to_char(): Do not count negative sign as a digit for time values
For time masks, like HH24, MI, SS, CC, MM, do not count the negative
sign as part of the zero-padding length specified by the mask, e.g. have
to_char('-4 years'::interval, 'YY') return '-04', not '-4'.
Report by Craig Ringer
Branch
Stamp 9.0.23.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/9a42e8514f7e42737992bb09bd93540dd9630a9a
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.1.19.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f0ceb25d04da0b672e16efd20fa30641b78ffe63
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.2.14.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/69157086413efb8c1de793aa4493187c819cc5ae
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.3.10.
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f5bbaeef1a5cdce1349ed6a1f87a85f17d741b56
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.4.5.
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/d25c7d70ff46d1b2f2400f29d100190efe84d70d
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.5beta1.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b96df2c61710b39d24e98767cfe17b920b9319a6
Modified Files
--
configure | 18 +-
configure.in |2 +-
doc/bug.template
docs: update guidelines on when to use GIN and GiST indexes
Report by Tomas Vondra
Backpatch through 9.5
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/7d88b3d15fe102ef6a006f1234025e91c7fa
Modified Files
--
doc/src/sgml/textsearch.sgml |
docs: update guidelines on when to use GIN and GiST indexes
Report by Tomas Vondra
Backpatch through 9.5
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/6d8b2aa83af70e20323caf23961667dc4c149276
Modified Files
--
doc/src/sgml/textsearch.sgml | 80
On Mon, Oct 5, 2015 at 4:55 AM, Stephen Frost wrote:
> Apply SELECT policies in INSERT/UPDATE+RETURNING
If we've changed this now, where does that leave the excluded.* pseudo-relation?
--
Peter Geoghegan
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make chan
Docs: explain contrib/pg_stat_statements' handling of GC failure.
Failure to perform garbage collection now has a user-visible effect, so
explain that and explain that reducing pgss_max is the way to prevent it.
Per gripe from Andrew Dunstan.
Branch
--
master
Details
---
http://git.postg
Docs: explain contrib/pg_stat_statements' handling of GC failure.
Failure to perform garbage collection now has a user-visible effect, so
explain that and explain that reducing pgss_max is the way to prevent it.
Per gripe from Andrew Dunstan.
Branch
--
REL9_5_STABLE
Details
---
http://gi
Docs: explain contrib/pg_stat_statements' handling of GC failure.
Failure to perform garbage collection now has a user-visible effect, so
explain that and explain that reducing pgss_max is the way to prevent it.
Per gripe from Andrew Dunstan.
Branch
--
REL9_4_STABLE
Details
---
http://gi
doc: Update URLs of external projects
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/bfbaeae48a9c927dca41c4ac73a8a7ca7ae7c6d5
Modified Files
--
doc/src/sgml/external-projects.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
-
doc: Update URLs of external projects
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/d3ff94d87cee5787aa6f9119cdc75ffc2507ec54
Modified Files
--
doc/src/sgml/external-projects.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
-
doc: Update URLs of external projects
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/ffdf2a20f177b5366e979e07cbfb05fe22edc06f
Modified Files
--
doc/src/sgml/external-projects.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
-
doc: Update URLs of external projects
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/cc0c8ec9fca50721beb1a36d43114e66b5d96825
Modified Files
--
doc/src/sgml/external-projects.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
-
doc: Update URLs of external projects
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/21369340f7c0d81a4473f552a1bf700c53224b5b
Modified Files
--
doc/src/sgml/external-projects.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 576bd3231176cdea570609e7fd16152bf2e5e15a
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/921c18c150b202a1ada974a3e2b963f23f2b0604
Modified Files
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 23a52bc86edcd39c3c6b80ee1f7374759c8711f8
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/149a8cdd7a299ce25eea9157baa636c3f00f2c5f
Modified Files
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: d8bd45466e3980b5ab4582ff1705fcd1fff42908
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f177e1bad326a329b168ecc03cdb61c28374a3a3
Modified Files
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: e0981ce6d26309e48891d9192c69fcccd40fe7cd
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f2bcd7a7ea57fba191b1f484b642481cc5cc824e
Modified Files
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 8e743278f47ca82f2af2c37eb8bb200bc8df2088
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e01548b5e2af51294263b336212abcf1d04ea2ca
Modified Files
-
Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: a985921768deca2a137f3bada7b3ea900201f661
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/5d250a80c0f4b67df6bd2ebd517536b6c4875911
Modified Files
-
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Remove outdated comment about relation level autovacuum freeze limits.
The documentation for the autovacuum_multixact_freeze_max_age and
autovacuum_freeze_max_age relation level parameters contained:
"Note that while you can set autovacuum_multixact_freeze_max_age very
small, or even zero, this is
Add regression tests for INSERT/UPDATE+RETURNING
This adds regressions tests which are specific to INSERT+RETURNING and
UPDATE+RETURNING to ensure that the SELECT policies are added as
WithCheckOptions (and should therefore throw an error when the policy is
violated).
Per suggestion from Andres.
Add regression tests for INSERT/UPDATE+RETURNING
This adds regressions tests which are specific to INSERT+RETURNING and
UPDATE+RETURNING to ensure that the SELECT policies are added as
WithCheckOptions (and should therefore throw an error when the policy is
violated).
Per suggestion from Andres.
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_0_STABLE
Details
--
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_2_STABLE
Details
--
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_4_STABLE
Details
--
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_3_STABLE
Details
--
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_1_STABLE
Details
--
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
REL9_5_STABLE
Details
--
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Prevent stack overflow in query-type functions.
The tsquery, ltxtquery and query_int data types have a common ancestor.
Having acquired check_stack_depth() calls independently, each was
missing at least one call. Back-patch to 9.0 (all supported versions).
Branch
--
master
Details
---
h
Prevent stack overflow in container-type functions.
A range type can name another range type as its subtype, and a record
type can bear a column of another record type. Consequently, functions
like range_cmp() and record_recv() are recursive. Functions at risk
include operator family members and
Apply SELECT policies in INSERT/UPDATE+RETURNING
Similar to 7d8db3e, given that INSERT+RETURNING requires SELECT rights
on the table, apply the SELECT policies as WCOs to the tuples being
inserted. Apply the same logic to UPDATE+RETURNING.
Back-patch to 9.5 where RLS was added.
Branch
--
ma
Apply SELECT policies in INSERT/UPDATE+RETURNING
Similar to 7d8db3e, given that INSERT+RETURNING requires SELECT rights
on the table, apply the SELECT policies as WCOs to the tuples being
inserted. Apply the same logic to UPDATE+RETURNING.
Back-patch to 9.5 where RLS was added.
Branch
--
RE
Do not write out WCOs in Query
The WithCheckOptions list in Query are only populated during rewrite and
do not need to be written out or read in as part of a Query structure.
Further, move WithCheckOptions to the bottom and add comments to clarify
that it is only populated during rewrite.
Back-p
Do not write out WCOs in Query
The WithCheckOptions list in Query are only populated during rewrite and
do not need to be written out or read in as part of a Query structure.
Further, move WithCheckOptions to the bottom and add comments to clarify
that it is only populated during rewrite.
Back-p
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
Re-Align *_freeze_max_age reloption limits with corresponding GUC limits.
In 020235a5754 I lowered the autovacuum_*freeze_max_age minimums to
allow for easier testing of wraparounds. I did not touch the
corresponding per-table limits. While those don't matter for the purpose
of wraparound, it seem
61 matches
Mail list logo
