Tighten test in contrib/bloom/t/001_wal.pl.
Make bloom WAL test compare psql output text, not just result codes;
this was evidently the intent all along, but it was mis-coded.
In passing, make sure we will notice any failure in setup steps.
Alexander Korotkov, reviewed by Michael Paquier and Masa
Tighten test in contrib/bloom/t/001_wal.pl.
Make bloom WAL test compare psql output text, not just result codes;
this was evidently the intent all along, but it was mis-coded.
In passing, make sure we will notice any failure in setup steps.
Alexander Korotkov, reviewed by Michael Paquier and Masa
Tighten test in contrib/bloom/t/001_wal.pl.
Make bloom WAL test compare psql output text, not just result codes;
this was evidently the intent all along, but it was mis-coded.
In passing, make sure we will notice any failure in setup steps.
Alexander Korotkov, reviewed by Michael Paquier and Masa
. This does have the
effect of moving read and write permission errors to happen at lo_open
time not loread or lowrite time, but that seems acceptable.
Michael Paquier and Tom Lane
Discussion:
https://postgr.es/m/cab7npqrhmnoybetnc_2ejsuzsm00z+bwkv9sy6tnvsd5gwt...@mail.gmail.com
Branch
Restrict lo_import()/lo_export() via SQL permissions not hard-wired checks.
While it's generally unwise to give permissions on these functions to
anyone but a superuser, we've been moving away from hard-wired permission
checks inside functions in favor of using the SQL permission system to
control
Fix typo in ALTER SYSTEM output.
The header comment written into postgresql.auto.conf by ALTER SYSTEM
should match what initdb put there originally.
Feike Steenbergen
Discussion:
https://postgr.es/m/CAK_s-G0KcKdO=0hqzkwb3s+tqzuuhwwqmf5bdsmoo9ftx75...@mail.gmail.com
Branch
--
REL9_5_STABLE
Fix typo in ALTER SYSTEM output.
The header comment written into postgresql.auto.conf by ALTER SYSTEM
should match what initdb put there originally.
Feike Steenbergen
Discussion:
https://postgr.es/m/CAK_s-G0KcKdO=0hqzkwb3s+tqzuuhwwqmf5bdsmoo9ftx75...@mail.gmail.com
Branch
--
REL_10_STABLE
Fix typo in ALTER SYSTEM output.
The header comment written into postgresql.auto.conf by ALTER SYSTEM
should match what initdb put there originally.
Feike Steenbergen
Discussion:
https://postgr.es/m/CAK_s-G0KcKdO=0hqzkwb3s+tqzuuhwwqmf5bdsmoo9ftx75...@mail.gmail.com
Branch
--
master
Detail
Fix typo in ALTER SYSTEM output.
The header comment written into postgresql.auto.conf by ALTER SYSTEM
should match what initdb put there originally.
Feike Steenbergen
Discussion:
https://postgr.es/m/CAK_s-G0KcKdO=0hqzkwb3s+tqzuuhwwqmf5bdsmoo9ftx75...@mail.gmail.com
Branch
--
REL9_4_STABLE
Fix typo in ALTER SYSTEM output.
The header comment written into postgresql.auto.conf by ALTER SYSTEM
should match what initdb put there originally.
Feike Steenbergen
Discussion:
https://postgr.es/m/CAK_s-G0KcKdO=0hqzkwb3s+tqzuuhwwqmf5bdsmoo9ftx75...@mail.gmail.com
Branch
--
REL9_6_STABLE
Fix bogus logic for checking executables' versions within pg_upgrade.
Somebody messed up a refactoring here. As it stood, we'd check pg_ctl's
--version output twice for each cluster. Worse, the first check for the
new cluster's version happened before we'd done any validate_exec checks
there, br
Fix bogus logic for checking executables' versions within pg_upgrade.
Somebody messed up a refactoring here. As it stood, we'd check pg_ctl's
--version output twice for each cluster. Worse, the first check for the
new cluster's version happened before we'd done any validate_exec checks
there, br
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
Revert "Allow --with-bonjour to work with non-macOS implementations of Bonjour."
Upon further review, our Bonjour code doesn't actually work with the
Avahi not-too-compatible compatibility library. While you can get it
to work on non-macOS platforms if you link to Apple's own mDNSResponder
code,
king. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/
king. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL9_2_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/203b965f275061894621a5a359213ac77558d33f
Modified Files
--
doc/src/sgml/release-9.2.sgml | 25
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/92d830f4bff643953a09563abaa106af42625207
Modified Files
--
doc/src/sgml/release-10.sgml | 108 ++
king. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/
king. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/fb3930ab1fdb53ad842307a47ddaa1fed4e85d5c
Modified Files
--
doc/src/sgml/release-9.2.sgml | 25
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e7bae63e02dee20fdcbad2664d4722c80febf8a1
Modified Files
--
doc/src/sgml/release-9.2.sgml | 25
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7b4c179b70a59ad2dbd5c928ce8fc84629da0237
Modified Files
--
doc/src/sgml/release-9.2.sgml | 25
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/50abeafc74a812d2449ec49dc16e99baf8c5023a
Modified Files
--
doc/src/sgml/release-10.sgml | 108 +++
Add tests for json{b}_populate_recordset() crash case.
The problem reported as CVE-2017-15098 was already resolved in HEAD by
commit 37a795a60, but let's add the relevant test cases anyway.
Michael Paquier and Tom Lane, per a report from David Rowley.
Security: CVE-2017-15098
B
king. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d69c0710a68068c7a415aaefd2c7d51f3197fe38
Modified Files
--
doc/src/sgml/release-9.2.sgml | 25
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
On macOS the relevant functions require no special library, but elsewhere
we need to pull in libdns_sd.
Back-patch to supported branches. No docs change since the docs do not
suggest that this is a Mac-only feature.
Luke Lo
Doc: fix erroneous example.
The grammar requires these options to appear the other way 'round.
jo...@posteo.de
Discussion: https://postgr.es/m/78933bd0-45ce-690e-b832-a328dd1a5...@posteo.de
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6c05b8150327ca5f58e
Doc: fix erroneous example.
The grammar requires these options to appear the other way 'round.
jo...@posteo.de
Discussion: https://postgr.es/m/78933bd0-45ce-690e-b832-a328dd1a5...@posteo.de
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bd65e0c62486e6108a7dc824f9
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/13492fcf9bb1a25034db3e5ec200a999b1efc371
Modified Files
--
src/backend/storage/buffer/bufmgr.c |
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c5269472ea9bb4a6fbb8a0510f7d676d725933ab
Modified Files
--
src/backend/storage/buffer/bufmgr.c | 2 +-
s
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b89ad383da7dfcf1c5888076d60bb914c6169ec6
Modified Files
--
src/backend/storage/buffer/bufmgr.c |
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/442bc4160caee01579f5c112c23d9bb5f121f6b6
Modified Files
--
src/backend/storage/buffer/bufmgr.c |
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d7f59347bc06cb26fe3eff283f9104ac1b26d177
Modified Files
--
src/backend/storage/buffer/bufmgr.c |
till,
back-patch to supported branches.
Thomas Munro and Tom Lane, per a comment from Andres Freund
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/1786cdab113701f154ca804537fe1c21d23e4ce8
Modified Files
--
src/backend/storage/buffer/bufmgr.c |
at changes.
That seems like a completely separate feature --- and one of dubious
value, frankly. The further back you go, the less likely it'd be
to work.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to y
resetxlog being able
to use WAL across a WAL format change, and there have been many of
those.
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
Fix unportable spelling of int64 constant.
Per buildfarm member pademelon.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/92a1834dd88e56e823ac6641313a2f077a8af72e
Modified Files
--
src/include/utils/hashutils.h | 2 +-
1 file changed, 1 insertion(+), 1
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix unportable usage of functions.
isdigit(), isspace(), etc are likely to give surprising results if passed a
signed char. We should always cast the argument to unsigned char to avoid
that. Error in commit 63d6b97fd, found by buildfarm member gaur.
Back-patch to 9.3, like that commit.
Branch
Fix version numbering foulups exposed by 10.1.
configure computed PG_VERSION_NUM incorrectly. (Coulda sworn I tested
that logic back when, but it had an obvious thinko.)
pg_upgrade had not been taught about the new dispensation with just
one part in the major version number.
Both things acciden
Fix version numbering foulups exposed by 10.1.
configure computed PG_VERSION_NUM incorrectly. (Coulda sworn I tested
that logic back when, but it had an obvious thinko.)
pg_upgrade had not been taught about the new dispensation with just
one part in the major version number.
Both things acciden
onth ends, a major version
receives one final minor release. After that final minor release, bug
fixing ceases for that major version.
(That para was recently reworded to be more specific, but this is what the
de facto policy has been since we established the five-year target.)
Peter Geoghegan writes:
> Tom Lane wrote:
>> Stamp 9.2.24.
> Uh, I thought 9.2 was EOL.
Now it is ...
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.po
Stamp 9.2.24.
Branch
--
REL9_2_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/8786f783ab2398468a8c4d8eac937fc6533d16e3
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 9.3.20.
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f3eff7b5c053735868c3967b7426d9f28d86873f
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 9.4.15.
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/de7dabfd35e8f657af9a54cb0ff3171e1cf8e957
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 9.5.10.
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9ce323f612ab19eda1322bb6cf8227b835027511
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 9.6.6.
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/0a13f1966d4cda2eb49dec0324ab5d482bbdd956
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 10.1.
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/0b35d54c6fc4d98f8e8b38770b53c7358ebf
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b390 and c29c57890
on these files, to reduce future maintenance issues. (I'd do it further
back, except that the 9.X branches differ anyway due to xlog-to-wal
link tag renaming.)
First-draft release notes for 10.1.
As usual, the release notes for other branches will be made by cutting
these down, but put them up for community review first. Note that a
fair percentage of the entries apply only to prior branches because
their issue was already fixed in 10.0.
Branch
--
Avoid looping through line pointers twice in PageRepairFragmentation().
There doesn't seem to be any good reason to do the filling of the
itemidbase[] array separately from the first traversal of the pointers.
It's certainly not a win if there are any line pointers with storage,
and even if there
Flag index metapages as standard-format in xlog.c calls.
btree, hash, and bloom indexes all set up their metapages in standard
format (that is, with pd_lower and pd_upper correctly delimiting the
unused area); but they mostly didn't inform the xlog routines of this.
When calling log_newpage[_buffe
Alvaro Herrera writes:
> Fix BRIN summarization concurrent with extension
Buildfarm is entirely unhappy ...
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.
pgbench: replace run-time string comparisons with an enum identifier.
Minor refactoring that should yield some performance benefit.
Fabien Coelho, reviewed by Aleksandr Parfenov
Discussion: https://postgr.es/m/alpine.DEB.2.20.1709230538130.4999@lancre
Branch
--
master
Details
---
https
Set the metapage's pd_lower correctly in brin, gin, and spgist indexes.
Previously, these index types left the pd_lower field set to the default
SizeOfPageHeaderData, which is really a lie because it ought to point past
whatever space is being used for metadata. The coding accidentally failed
to
n, perhaps, a month, once
the dust is entirely settled.
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
u're all tired of hearing me say this) patches that
> implicate the on-disk format are scary.
Agreed, but how is that relevant now that the bogus patches are reverted?
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To m
Fix corner-case errors in brin_doupdate().
In some cases the BRIN code releases lock on an index page, and later
re-acquires lock and tries to check that the tuple it was working on is
still there. That check was a couple bricks shy of a load. It didn't
consider that the page might have turned i
Fix corner-case errors in brin_doupdate().
In some cases the BRIN code releases lock on an index page, and later
re-acquires lock and tries to check that the tuple it was working on is
still there. That check was a couple bricks shy of a load. It didn't
consider that the page might have turned i
Fix corner-case errors in brin_doupdate().
In some cases the BRIN code releases lock on an index page, and later
re-acquires lock and tries to check that the tuple it was working on is
still there. That check was a couple bricks shy of a load. It didn't
consider that the page might have turned i
Fix corner-case errors in brin_doupdate().
In some cases the BRIN code releases lock on an index page, and later
re-acquires lock and tries to check that the tuple it was working on is
still there. That check was a couple bricks shy of a load. It didn't
consider that the page might have turned i
Teach planner to account for HAVING quals in aggregation plan nodes.
For some reason, we have never accounted for either the evaluation cost
or the selectivity of filter conditions attached to Agg and Group nodes
(which, in practice, are always conditions from a HAVING clause).
Applying our regul
Andres Freund writes:
> Do we care about people upgrading to unreleased versions? We could do
> nothing, document it in the release notes, or ???
Do nothing.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make c
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL9_2_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/13406fe23d3c6f3889014df6c001eb8652114a64
Modifie
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e89867c033291b01614cb1a0e6fe76ce4c478ea6
Modifie
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/1048afc864e84b4f206bb7edd3773b49f1d8cc5b
Modifie
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7ae39519bf0eca229f7ae98a391b161c43fe88a9
Modifie
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f570ec5181e1aeff4fc8ea229e50bd666d35062f
Modifie
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c0e2062d3214f6230a0e1eee9236b202bda9221f
Modified Files
Doc: update URL for check_postgres.
Reported by Dan Vianello.
Discussion:
https://postgr.es/m/e6e12f18f70e46848c058084d42fb...@kstlmexgp001.corp.chartercom.com
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/1cf96d6c7169d0eb21770eac67b60c12dcaf113c
Modifie
Allow bitmap scans to operate as index-only scans when possible.
If we don't have to return any columns from heap tuples, and there's
no need to recheck qual conditions, and the heap page is all-visible,
then we can skip fetching the heap page altogether.
Skip prefetching pages too, when possible
Fix ALTER TABLE code to update domain constraints when needed.
It's possible for dropping a column, or altering its type, to require
changes in domain CHECK constraint expressions; but the code was
previously only expecting to find dependent table CHECK constraints.
Make the necessary adjustments.
t to search_path
rules, but it seems better to use uniform style.
Vitaly Burovoy and Tom Lane
Discussion:
https://postgr.es/m/CAKOSWN=ds66zlw2sqkltm8wbxfgdbc_odkmt3djfpt2me5k...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/080351466c5a669bf35a323bd
t to search_path
rules, but it seems better to use uniform style.
Vitaly Burovoy and Tom Lane
Discussion:
https://postgr.es/m/CAKOSWN=ds66zlw2sqkltm8wbxfgdbc_odkmt3djfpt2me5k...@mail.gmail.com
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9cf2b8
Doc: call out UPDATE syntax change as a v10 compatibility issue.
The change made by commit 906bfcad7 means that if you're writing
a parenthesized column list in UPDATE ... SET, but that column list
is only one column, you now need to write ROW(expression) on the
righthand side, not just a parenthe
Doc: call out UPDATE syntax change as a v10 compatibility issue.
The change made by commit 906bfcad7 means that if you're writing
a parenthesized column list in UPDATE ... SET, but that column list
is only one column, you now need to write ROW(expression) on the
righthand side, not just a parenthe
Support domains over composite types in PL/Perl.
In passing, don't insist on rsi->expectedDesc being set unless we
actually need it; this allows succeeding in a couple of cases where
PL/Perl functions returning setof composite would have failed before,
and makes the error message more apropos in o
Dept of second thoughts: keep aliasp_item in sync with tlistitem.
Commit d5b760ecb wasn't quite right, on second thought: if the
caller didn't ask for column names then it would happily emit
more Vars than if the caller did ask for column names. This
is surely not a good idea. Advance the aliasp
1 - 100 of 19184 matches
Mail list logo
