The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/ddl-generated-columns.html
Description:
On page https://www.postgresql.org/docs/current/ddl-generated-columns.html :
In the example "CREATE TABLE people" ...,
the line "GENERATED ALWAYS A
On Wednesday, October 1, 2025, David G. Johnston
wrote:
> On Wednesday, October 1, 2025, yanliang lei wrote:
>>
>> dbversion180=# create table schema_1.test_tab_100(c1 int default
>> nextval('seq_xx_yy'));
>>
>
> Since you didn’t schema qualify the sequence name every single time a
> default val
On Tue Oct 7, 2025 at 6:08 PM CEST, Dmitry Igrishin wrote:
CancelRequest(F) documentation at
https://www.postgresql.org/docs/18/protocol-message-formats.html#PROTOCOL-MESSAGE-FORMATS-CANCELREQUEST
seems to be inconsistent for protocol 3.2. It is stated here that the
length of the message is alway
On Tue, 2025-10-14 at 12:14 +, PG Doc comments form wrote:
> The description of BPCHAR in section 8.3. Character Types is
> misleading and
> incomplete.
Hi,
There was a previous discussion here:
https://www.postgresql.org/message-id/E1odZyZ-g2-AE%40gemulon.postgresql.org
> The first pro
The logs that were printed by Postgres
when enforcing deferred unique indexes were misleading.
This change should make it easier to understand or investigate
when users see the `waits for ShareLock` log entry
---
doc/src/sgml/mvcc.sgml | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/
On Wed, Oct 1, 2025 at 6:04 AM yanliang lei wrote:
> the column c1 in the schema_1.test_tab_100 is associated with which
> sequence ?? *schema_1*.seq_xx_yy or *public*.seq_xx_yy??
>
This is better asked on the pgsql-general mailing list, but the short
answer is that you have to look at your sea
On Thu, Oct 16, 2025 at 11:18 PM David G. Johnston
wrote:
>> > Think of padding as a noun, not a verb. “The value contains padding”.
>> > Not, “ I am padding the value”.
>
> In PostgreSQL the behavior and stored contents/representation of a value are
> not influenced by a type modifier. It i
> On 7 Oct 2025, at 14:27, Shinya Kato wrote:
> Attached is a doc-only fix that adds a missing closing parenthesis in
> monitoring.sgml (pg_stat_progress_analyze: delay_time).
Thanks, will fix (with a backpatch to 18).
--
Daniel Gustafsson
On Thursday, October 16, 2025, Sergei Katkovsky
wrote:
> > I don't understand why any of these variants are better than the
> > original wording "blank-padded". That has the non-negligible
> > advantage of corresponding to the type name, and furthermore
> > appears in many other places in our do
hi ，everyone，
my postgresql version is 18.0,
in the different schema ，the sequence name is same， and a table‘s column
definition use this sequence，
so，how can I identify sequence's schema name by system view/table?
the following is example:
[pg180@kunpeng3 ~]$ psql -d postgres -U pg180 -p 5
Thank you for your feedback, Daniel.
My thoughts are below:
/- Change the definition of a replication slot. + Changes the definition
of a replication slot. Reading this page it seems we are mixing tense in
many places, some say "Change the" and "Read some" and elsewhere we use
"Drops the". Ma
On Monday, September 29, 2025, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/ddl-generated-columns.html
> Description:
>
> On page https://www.postgresql.org/docs/current/ddl-generated-columns.html
>
On Wednesday, October 1, 2025, yanliang lei wrote:
>
> dbversion180=# create table schema_1.test_tab_100(c1 int default
> nextval('seq_xx_yy'));
>
Since you didn’t schema qualify the sequence name every single time a
default value is created the sequence will be looked up anew. The stored
expres
On Thursday, October 16, 2025, Sergei Katkovsky
wrote:
> Manual addition is not padding, If it were, then VARCHAR would also be
> "blank-padded", because you can manually add trailing blanks to values
> of this type too. But of course it isn't.
>
The spaces added to the end of a bpchar manually
On Mon, 13 Oct 2025 at 11:57, Jelte Fennema-Nio wrote:
> On Tue Oct 7, 2025 at 6:08 PM CEST, Dmitry Igrishin wrote:
> > CancelRequest(F) documentation at
> >
> https://www.postgresql.org/docs/18/protocol-message-formats.html#PROTOCOL-MESSAGE-FORMATS-CANCELREQUEST
> > seems to be inconsistent for
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/datatype-character.html
Description:
The description of BPCHAR in section 8.3. Character Types is misleading and
incomplete.
The first problem is that, contrary to table 8.4, BPCHAR is not
PG Doc comments form writes:
> I was connected to database via `psql` then I rebooted DB. I was not able to
> disconnect from terminal after that. Only whole window close helped.
A documentation comment is a very poor way to submit a trouble
report...
> FATAL: terminating connection due to admi
On Thursday, October 16, 2025, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/app-psql.html
> Description:
>
> Hello.
> I was connected to database via `psql` then I rebooted DB. I was not able
> to
>
On Tue, 23 Sept 2025 at 20:59, PG Doc comments form
wrote:
> Page: https://www.postgresql.org/docs/17/datatype-enum.html
> Description:
>
> In section 8.7.3. Type Safety one can observe a the following statement in
> the examples.
>
> INSERT INTO holidays(num_weeks,happiness) VALUES (2, 'sad');
>
On Thursday, October 16, 2025, Sergei Katkovsky
wrote:
> On Thu, Oct 16, 2025 at 11:18 PM David G. Johnston
> wrote:
>
> >> > Think of padding as a noun, not a verb. “The value contains
> padding”. Not, “ I am padding the value”.
> >
> I'm afraid that adding
> another meaning to the word 'pa
20 matches
Mail list logo
