Andres Freund writes:
> Add CASCADE support for CREATE EXTENSION.
Buildfarm results suggest this was not tested with python 3.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www
Update 9.5 release notes through today.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/cf007a4bca59a1bca6951351e10ff227d2b0c10a
Modified Files
--
doc/src/sgml/release-9.5.sgml | 63 ++---
1 file changed, 59 insertions
First-draft release notes for 9.4.5, 9.3.10, 9.2.14, 9.1.19, 9.0.23.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/01ef33701bf6d475deeb550c18a5c3fd698c9623
Modified Files
--
doc/src/sgml/release-9.4.sgml | 1446 +
Document that row_security is a boolean GUC.
Oversight in commit 537bd178c73b1d25938347b17e9e3e62898fc231.
Back-patch to 9.5, like that commit.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4365d9c18fc1ebb14de92595aa0340c5b8301547
Modified Files
---
Document that row_security is a boolean GUC.
Oversight in commit 537bd178c73b1d25938347b17e9e3e62898fc231.
Back-patch to 9.5, like that commit.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f78ae3747d8bdf07d864e465eb257ad5b7fd825a
Modified Files
--
doc
Make BYPASSRLS behave like superuser RLS bypass.
Specifically, make its effect independent from the row_security GUC, and
make it affect permission checks pertinent to views the BYPASSRLS role
owns. The row_security GUC thereby ceases to change successful-query
behavior; it can only make a query
Make BYPASSRLS behave like superuser RLS bypass.
Specifically, make its effect independent from the row_security GUC, and
make it affect permission checks pertinent to views the BYPASSRLS role
owns. The row_security GUC thereby ceases to change successful-query
behavior; it can only make a query
Add missed CREATE EXTENSION ... CASCADE regression test adjustment.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/23fc0b485d6dfa49ff20fff6c5661be4b12a5bff
Modified Files
--
contrib/earthdistance/expected/earthdistance.out |1 +
1 file changed, 1 inse
On 2015-10-03 12:24:57 -0700, Peter Geoghegan wrote:
> On Sat, Oct 3, 2015 at 9:48 AM, Andres Freund wrote:
> > Add CASCADE support for CREATE EXTENSION.
>
> As you may have noticed already, this patch fails to account for this
> change in earthdistance regression test output:
>
> + HINT: Use C
On Sat, Oct 3, 2015 at 9:48 AM, Andres Freund wrote:
> Add CASCADE support for CREATE EXTENSION.
As you may have noticed already, this patch fails to account for this
change in earthdistance regression test output:
+ HINT: Use CREATE EXTENSION CASCADE to install required extensions too.
--
P
Add CASCADE support for CREATE EXTENSION.
Without CASCADE, if an extension has an unfullfilled dependency on
another extension, CREATE EXTENSION ERRORs out with "required extension
... is not installed". That is annoying, especially when that dependency
is an implementation detail of the extension
Add missing "static" specifier.
Per buildfarm (pademelon, at least, doesn't like this).
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/bf686796a055a8bd4abc9765763eb675a0428473
Modified Files
--
src/backend/executor/nodeGather.c |2 +-
1 file changed,
Improve errhint() about replication slot naming restrictions.
The existing hint talked about "may only contain letters", but the
actual requirement is more strict: only lower case letters are allowed.
Reported-By: Rushabh Lathia
Author: Rushabh Lathia
Discussion: agpqqf2x50qcwbyobkzb4x75so_v3g81z
Improve errhint() about replication slot naming restrictions.
The existing hint talked about "may only contain letters", but the
actual requirement is more strict: only lower case letters are allowed.
Reported-By: Rushabh Lathia
Author: Rushabh Lathia
Discussion: agpqqf2x50qcwbyobkzb4x75so_v3g81z
Improve errhint() about replication slot naming restrictions.
The existing hint talked about "may only contain letters", but the
actual requirement is more strict: only lower case letters are allowed.
Reported-By: Rushabh Lathia
Author: Rushabh Lathia
Discussion: agpqqf2x50qcwbyobkzb4x75so_v3g81z
Fix several bugs related to ON CONFLICT's EXCLUDED pseudo relation.
Four related issues:
1) attnos/varnos/resnos for EXCLUDED were out of sync when a column
after one dropped in the underlying relation was referenced.
2) References to whole-row variables (i.e. EXCLUDED.*) lead to errors.
3) It
Fix several bugs related to ON CONFLICT's EXCLUDED pseudo relation.
Four related issues:
1) attnos/varnos/resnos for EXCLUDED were out of sync when a column
after one dropped in the underlying relation was referenced.
2) References to whole-row variables (i.e. EXCLUDED.*) lead to errors.
3) It
On Sat, Oct 3, 2015 at 1:37 AM, Magnus Hagander wrote:
> Should we consider backpatching this further into the stable branches?
> Arguably it's a bugfix given the state of pgfoundry.
+1
--
Peter Geoghegan
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make ch
Should we consider backpatching this further into the stable branches?
Arguably it's a bugfix given the state of pgfoundry.
//Magnus
On Sat, Oct 3, 2015 at 3:55 AM, Peter Eisentraut wrote:
> doc: Update URLs of external projects
>
> Branch
> --
> REL9_5_STABLE
>
> Details
> ---
>
> http
19 matches
Mail list logo
