Fix the SharedFileSetUnregister API.
Commit 808e13b282 introduced a few APIs to extend the existing Buffile
interface. In SharedFileSetDeleteOnProcExit, it tries to delete the list
element while traversing the list with 'foreach' construct which makes the
behavior of list traversal unpredictable.
doc: document how the backup manifest is transferred
Reported-by: Bernd Helmle
Discussion:
https://postgr.es/m/31acf8b0f1f701d53245e0cae38abdf5c3a0d559.ca...@oopsware.de
Backpatch-through: 13
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/73018f564af91b1
doc: document how the backup manifest is transferred
Reported-by: Bernd Helmle
Discussion:
https://postgr.es/m/31acf8b0f1f701d53245e0cae38abdf5c3a0d559.ca...@oopsware.de
Backpatch-through: 13
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ab3c6d41552411ea2fe490
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
doc: add commas after 'i.e.' and 'e.g.'
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/202008251836
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/160c8a4d382204ca2983aba56cc9e5db716735
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e4263c4a569ef0be28e7fc471280837147f82a
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7d26d85f1b95806985cbc739428f929204d852
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/787ccf5a5fc92698e8cc8ebfb6fe1a0bf28981
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/fd9451d201d00d20f2f043355b25e0f8d85bf9
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b1f52817bcdc3a6d269d4bd9b4d02a635e5d39
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
https://git.p
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
https://git.p
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
https://git.p
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
https://git.p
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
https://git.p
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
master
Details
---
https://git.postgres
pg_upgrade doc: mention saving postgresql.conf.auto files
Also mention files included by postgresql.conf.
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/08ad4526-75ab-457b-b2dd-099663f28...@yesql.se
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
https://git.p
doc: Update partitioning limitation on BEFORE triggers
Reported-by: Erwin Brandstetter
Discussion:
https://postgr.es/m/CAGHENJ6Le7S3qJJx2TvWvTwRNS3N=btoneb7af2rzvfnbme...@mail.gmail.com
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/97dc0d1d58916e2f063ce8a
doc: Update partitioning limitation on BEFORE triggers
Reported-by: Erwin Brandstetter
Discussion:
https://postgr.es/m/CAGHENJ6Le7S3qJJx2TvWvTwRNS3N=btoneb7af2rzvfnbme...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/0ebe82a9413fcd5621266ec57d9f4b
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
https://git.p
docs: in mapping SQL to C data types, timestamp isn't a pointer
It is an int64.
Reported-by: ajul...@shaktiware.fr
Discussion:
https://postgr.es/m/159845038271.24995.15682121015698255...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
master
Details
---
https://git.postgres
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
doc: cross-link file-fdw and CSV config log sections
There is an file-fdw example that reads the server config file, so cross
link them.
Reported-by: Oleg Samoilov
Discussion:
https://postgr.es/m/159800192078.2886.10431506404995508...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/892
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/361
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b1ae70b3b4
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/075
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/bdf
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/01b
docs: clarify intermediate certificate creation instructions
Specifically, explain the v3_ca openssl specification.
Discussion: https://postgr.es/m/20200824175653.ga32...@momjian.us
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a85
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage"
does not, so use the former.
Discussion: https://postgr.es/m/20200817165222.ga31...@momjian.us
Backpatch-through: 9.5
Branch
--
master
Details
---
https:
C comment: remove mention of use of t_hoff WAL structure member
Reported-by: Antonin Houska
Discussion: https://postgr.es/m/21643.1595353537@antos
Backpatch-through: 9.5
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/1e0512ff23e600e9bc19e7f1a1c5ce0597c7bd47
Mod
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
doc: improve description of subscripting of arrays
It wasn't clear the non-integers are cast to integers for subscripting,
rather than throwing an error.
Reported-by: s...@materialize.io
Discussion:
https://postgr.es/m/159538675800.624.7728794628229799...@wrigleys.postgresql.org
Backpatch-thr
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
master
Details
---
https://git.postgresql.
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_10_STABLE
Details
---
https://git.post
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL9_6_STABLE
Details
---
https://git.post
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_12_STABLE
Details
---
https://git.post
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_13_STABLE
Details
---
https://git.post
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL9_5_STABLE
Details
---
https://git.post
docs: improve 'capitals' inheritance example
Adds constraints and improves wording.
Reported-by: 2552...@gmail.com
Discussion:
https://postgr.es/m/159586122762.680.1361378513036616...@wrigleys.postgresql.org
Backpatch-through: 9.5
Branch
--
REL_11_STABLE
Details
---
https://git.post
doc: clarify the useful features of procedures
This was not clearly documented when procedures were added in PG 11.
Reported-by: Robin Abbi
Discussion:
https://postgr.es/m/CAGmg_NX327KKVuJmbWZD=pGutYFxzZjX1rU+3ji8UuX=8on...@mail.gmail.com
Backpatch-through: 11
Branch
--
master
Details
-
doc: clarify the useful features of procedures
This was not clearly documented when procedures were added in PG 11.
Reported-by: Robin Abbi
Discussion:
https://postgr.es/m/CAGmg_NX327KKVuJmbWZD=pGutYFxzZjX1rU+3ji8UuX=8on...@mail.gmail.com
Backpatch-through: 11
Branch
--
REL_13_STABLE
De
doc: clarify the useful features of procedures
This was not clearly documented when procedures were added in PG 11.
Reported-by: Robin Abbi
Discussion:
https://postgr.es/m/CAGmg_NX327KKVuJmbWZD=pGutYFxzZjX1rU+3ji8UuX=8on...@mail.gmail.com
Backpatch-through: 11
Branch
--
REL_11_STABLE
De
doc: clarify the useful features of procedures
This was not clearly documented when procedures were added in PG 11.
Reported-by: Robin Abbi
Discussion:
https://postgr.es/m/CAGmg_NX327KKVuJmbWZD=pGutYFxzZjX1rU+3ji8UuX=8on...@mail.gmail.com
Backpatch-through: 11
Branch
--
REL_12_STABLE
De
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
Fix docs bug stating file_fdw requires absolute paths
It has always (since the first commit) worked with relative paths, so
use the same wording as other parts of the documentation.
Author: Bruce Momjian
Discussion:
https://postgr.es/m/CABUevExx-hm=cit+a9lekbh39srvk8y2tezeeaj5mp8yfzn...@mail.gma
79 matches
Mail list logo