On Wed, Aug 17, 2022 at 2:58 PM Bruce Momjian wrote:
> On Wed, Aug 17, 2022 at 12:41:03PM -0400, Jeff Janes wrote:
> > This was recently added to CREATE INDEX reference page:
> >
> > +The optional USING clause specifies an index
> >
This was recently added to CREATE INDEX reference page:
+The optional USING clause specifies an index
+type as described in . If not
+specified, a default index type will be used based on the
+data types of the columns.
But I think this is wrong, the default type
On Wed, Oct 7, 2020 at 5:47 PM David G. Johnston
wrote:
> On Wed, Oct 7, 2020 at 2:35 PM Jeff Janes wrote:
>
>> Quoting the docs:
>>
>> https://www.postgresql.org/docs/13/continuous-archiving.html
>>
>> "As with base backups, the easiest way to pro
Quoting the docs:
https://www.postgresql.org/docs/13/continuous-archiving.html
"As with base backups, the easiest way to produce a standalone hot backup
is to use the pg_basebackup tool. If you include the -X parameter when
calling it, all the write-ahead log required to use the backup will be
On Thu, Dec 19, 2019 at 11:43 AM Bruce Momjian wrote:
> On Wed, Nov 27, 2019 at 11:33:03AM -0500, Jeff Janes wrote:
> > I think that the permissions around the usage of foreign server names as
> > connection names in dblink should be documented, as in the attached.
>
> Uh, t
I think that the permissions around the usage of foreign server names as
connection names in dblink should be documented, as in the attached.
Also, for dblink itself it says "It is recommended to use the foreign-data
wrapper dblink_fdw when defining the foreign server". Is there a reason
for
If you alter one of the built-in text search configurations, the
modifications to it will not get dumped by pg_dump, and thus won't get
propagated by pg_upgrade leading to silent behavior changes in the new
cluster (as well in any other type of restoration from pg_dump output)
I would say it is
https://www.postgresql.org/docs/current/wal-async-commit.html:
"If the database crashes during the risk window between an asynchronous
commit and the writing of the transaction's WAL records, then changes made
during that transaction will be lost. The duration of the risk window is
limited
The section on dynamic SQL recommends "format", but the cross link goes to
the top of page 9.4 not the "format" specific 9.4.1.
This is particularly confusing as 9.4 only has one sub-section, so the TOC
at the top of the page only has one entry. This makes it look more like a
section header
