Re: PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4

On Sat, May 31, 2025 at 2:14 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > It's quite annoying that you didn't just copy the relevant SQL commands > and error messages into the email. Having to go through file share and > deal with images is quite annoying. > Although I suppose see

Re: PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4

On Sat, May 31, 2025 at 1:23 PM LUC PHEMBA wrote: > Can then someone explain me why the same format works in this case : > > *https://transfert.free.fr/P6wOY5x * > > but not in this other one : > > *https://transfert.free.fr/66abCAs

PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4

Hi, According to the official PosgreSQL 17 documentation (https://www.postgresql.org/docs/current/ddl-default.html), default values are listed after the column data type following this format : *column_name column_data_type DEFAULT default_value* For example : *price numeric DEFAULT 9.99* (whe

Re: LC_COLLATE is visible in the documentation for PostgreSQL 17, but it is not supported

On Sat, Jan 4, 2025 at 11:53 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-show.html > Description: > > On the docs page for SHOW > (https://www.postgresql.org/docs/17/sql-show.html), LC_COLLA

LC_COLLATE is visible in the documentation for PostgreSQL 17, but it is not supported

LC_COLLATE on PG 17 results in the following: ERROR: unrecognized configuration parameter "lc_collate" And according to Laurenz it has been removed in PostgreSQL 16 already: https://stackoverflow.com/a/77979710/2323727 I've never contributed to the docs, but I'm open to making

Re: PostgreSQL limits

tement length that > PostgreSQL can handle > in the Appendix K. PostgreSQL Limits. > If I'm not wrong it is 2147483648 that is a quite large number, larger than > many other RDBMS. Uh, we can add it, but we try to only list limits that are likely to be exceeded. -- Bruce Momjia

PostgreSQL limits

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/limits.html Description: I think it can be useful to add the maximum SQL statement length that PostgreSQL can handle in the Appendix K. PostgreSQL Limits. If I'm not wrong

Re: Re: Supplements and suggestions and about postgresql sequence setval function in the documents

On Thu, 22 Aug 2024 at 11:41, yanliang lei wrote: > What I want to express is： >There is no description in the document that the schema name can be > included before the sequence name I'm not to sure there is any problem here. If you look at the final paragraph in: https://www.postgresql.org

Re: Re: Supplements and suggestions and about postgresql sequence setval function in the documents

On Wed, Aug 21, 2024 at 4:41 PM yanliang lei wrote: > What I want to express is： >There is no description in the document that the schema name can be > included before the sequence name > > > Correct. It is here: All of the OID alias types for objects that are grouped by namespace accept sc

Re:Re: Supplements and suggestions and about postgresql sequence setval function in the documents

What I want to express is： There is no description in the document that the schema name can be included before the sequence name 在 2024-08-21 21:01:35，"David G. Johnston" 写道： On Wednesday, August 21, 2024, yanliang lei wrote: in the following example; select setval('seq_

Re: Typo on 2.3. PostgreSQL

PG Doc comments form writes: > In https://www.postgresql.org/docs/16/history.html#HISTORY-POSTGRESQL, > Chapter 2.3. PostgreSQL is written in first sentence: "By 1996, it became > clear that the name “Postgres95” would not stand the test of time." > I think there shoul

Typo on 2.3. PostgreSQL

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/history.html Description: In https://www.postgresql.org/docs/16/history.html#HISTORY-POSTGRESQL, Chapter 2.3. PostgreSQL is written in first sentence: "By 1996, it became clear tha

Re: Supplements and suggestions and about postgresql sequence setval function in the documents

On Wednesday, August 21, 2024, yanliang lei wrote: > > > in the following example; > select setval('seq_test',111); > ---this setval('seq_test',111) : update the current schema's seq_test > last_value =111 > > select setval('schemalei.seq_test',222); > ---this setval('seq_test',111) : update

Supplements and suggestions and about postgresql sequence setval function in the documents

222 (2 rows) postgres=# select version(); version - PostgreSQL 16.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 7.3.0, 64-bit (1 row) postgres=#

Re: incorrect PostgreSQL documentation for pg_type

On Sat, 3 Aug 2024 at 02:54, PG Doc comments form wrote: > Table 51.63. pg_type Columns > NameTypeReferences > --- > typinputregproc pg_proc.oid > typoutput regproc pg_proc.oid > typreceive regproc pg_pr

Re: incorrect PostgreSQL documentation for pg_type

PG Doc comments form writes: > There is an error in the documentation, at least for version 12 (cannot > check for version 16), in the ‘References ‘ column, for the following > entries: > Table 51.63. pg_type Columns > Name TypeReferences > --- >

incorrect PostgreSQL documentation for pg_type

pg_proc.oid typsend regproc pg_proc.oid typmodinregproc pg_proc.oid typmodout regproc pg_proc.oid typanalyze regproc pg_proc.oid The correct reference is pg_proc.proname select VERSION(); PostgreSQL 12.14 on aarch64-unknown-linux-gnu, compiled

Re: 52.38 pg_proc (postgresql version 14)

On Mon, 2024-05-20 at 21:07 +, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/14/catalog-pg-proc.html > Description: > > I don't know if this is a documentation problem or an error in pg_proc. > > The document, for the "prokind" column state the following: > f for

52.38 pg_proc (postgresql version 14)

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/catalog-pg-proc.html Description: I don't know if this is a documentation problem or an error in pg_proc. The document, for the "prokind" column state the following: f for a normal

Fundamental Architecture of PostgreSQL

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/tutorial-arch.html Description: PostgreSQL uses a client/server architecture. As is typical of client/server applications, the client and the server can be on different hosts. In that

Re: The PostgreSQL Select Syntax

core structure and rules for constructing valid queries. However, I'm interested in building an Object-Relational Mapper (ORM) for PostgreSQL. My primary question is: Does the documented formal syntax represent the absolute limit of what PostgreSQL can understand and process, or are there

The PostgreSQL Select Syntax

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/sql-select.html Description: Dear PostgreSQL Team, I'm writing to seek clarification regarding the scope of the formal syntax outlined in the documentation for the SELECT stat

Re: Need a PostgreSQL 16 developer edition for enabling vector support

On Thu, 4 Apr 2024 at 19:48, PG Doc comments form wrote: > We want to compile a vector extension in the postgres 16 dev edition and > use > the vector feature in the PostgreSQL You'll be better joining the pgsql-general [1] mailing list to ask this sort of question. The tool you&

Need a PostgreSQL 16 developer edition for enabling vector support

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/bug-reporting.html Description: Need a PostgreSQL 16 developer edition for enabling vector support. We want to compile a vector extension in the postgres 16 dev edition and use the

Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual

On 23.02.24 12:23, 小泉 悟 wrote: Upon closer inspection, F305 is also "INTERSECT ALL table operator”. Perhaps F302-02 would be unnecessary. Correct, F302-02 should have been deleted. I have fixed it, thanks. 2024/02/23 18:06、Daniel Gustafsson のメール: On 23 Feb 2024, at 06:36, PG Doc comments

Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual

> On 23 Feb 2024, at 12:23, 小泉 悟 wrote: > Upon closer inspection, F305 is also "INTERSECT ALL table operator”. > Perhaps F302-02 would be unnecessary. The list is intended to reflect what's in the SQL:2023 standard, so whatever the standard says we should too. I don't have a copy of the standar

Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual

Upon closer inspection, F305 is also "INTERSECT ALL table operator”. Perhaps F302-02 would be unnecessary. > 2024/02/23 18:06、Daniel Gustafsson のメール: > >> On 23 Feb 2024, at 06:36, PG Doc comments form >> wrote: > >> The correct result would be as follows: >> >> F302 INTERSECT table operato

Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual

> On 23 Feb 2024, at 06:36, PG Doc comments form wrote: > The correct result would be as follows: > > F302 INTERSECT table operator > F302-02 INTERSECT ALL table operator > F303 INTERSECT DISTINCT table operator > F304 EXCEPT ALL tab

incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/features-sql-standard.html Description: In "D.1. Supported Features"(https://www.postgresql.org/docs/current/features-sql-standard.html), identifiers appear as following: F302

Integration of Comprehensive PostgreSQL Extension Development Tutorial

Hi, I am reaching out for some input regarding the integration of a comprehensive PostgreSQL extension development tutorial <https://github.com/IshaanAdarsh/Postgres-extension-tutorial/blob/main/SGML/intro_and_toc.md> that I've been working on as part of the GSoC 2023 pro

Re: U+200B ZERO WIDTH SPACE (0xe2 0x80 0x8b) in PostgreSQL documentation

PG Doc comments form writes: > In official html documentation there are issue U+200B ZERO WIDTH SPACE (0xe2 > 0x80 0x8b) in text of some keywords, some identificators and some literals. > When copy-pasting to the SQL command, an error occurs because of this. > For example in page infoschema-admin

U+200B ZERO WIDTH SPACE (0xe2 0x80 0x8b) in PostgreSQL documentation

{/usr/share/doc/postgresql-doc-13/html/infoschema-administrable-role-authorizations.html}. See below excerpt text from the abovementioned page contains: administrable_role_<200b>authorizations

Re: PostgreSQL 16 release notes: could cloud

On Mon, Jun 5, 2023 at 07:12:35PM +0200, Erik Rijkers wrote: > Op 6/5/23 om 17:44 schreef Bruce Momjian: > > On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote: > > > > > > > I guess one "could" should be enough? > > > > That has been fixed, but unfortunately the copies of

Re: PostgreSQL 16 release notes: could cloud

Op 6/5/23 om 17:44 schreef Bruce Momjian: On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote: I guess one "could" should be enough? That has been fixed, but unfortunately the copies of the release notes on the community website are unchanged since beta1 was packaged; p

Re: PostgreSQL 16 release notes: could cloud

Thanks, Bruce From: Bruce Momjian Sent: Monday, June 5, 2023 17:44 To: Daniel Westermann (DWE) Cc: pgsql-docs@lists.postgresql.org Subject: Re: PostgreSQL 16 release notes: could cloud On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote

Re: PostgreSQL 16 release notes: could cloud

On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote: > Hi, > > E.1.3.1.4. Privileges # > > Simplify permissions for LOCK TABLE (Jeff Davis) > > Previously the ability to perform LOCK TABLE at various lock levels was bound > to specific query-type permissions. For example, UP

PostgreSQL 16 release notes: could cloud

Hi, E.1.3.1.4. Privileges # Simplify permissions for LOCK TABLE (Jeff Davis) Previously the ability to perform LOCK TABLE at various lock levels was bound to specific query-type permissions. For example, UPDATE could could perform all lock levels except ACCESS SHARE, which required SELECT perm

Misleading description for IPC wait events in PostgreSQL documentation

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/monitoring-stats.html Description: While preparing for my presentation on PostgreSQL Wait Events at PgConf India, I was trying to understand *IPC:XactGroupUpdate* in more detail

Misleading description for IPC wait events in PostgreSQL documentation

Hi, While preparing for my presentation on PostgreSQL Wait Events at PgConf India, I was trying to understand *IPC:XactGroupUpdate* in more detail. PostgreSQL documentation [1] mentions: > A process is waiting for the group leader to update the transaction status at the end of a _paral

Re: There is no command pg_ctl reload in Postgresql 13 clusters

PG Doc comments form writes: > Could you provide additional information about pg_ctlcluster command? pg_ctlcluster is not part of the community Postgres code. It is (I believe) added by the Debian packagers, so you'd have to discuss the state of their documentation with them.

There is no command pg_ctl reload in Postgresql 13 clusters

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/config-setting.html Description: Could you provide additional information about pg_ctlcluster command? On postgrsql 13 clusters there is no pg_ctl reload. So we should not use `pg_ctl rel

Re: wiki postgresql Window_function some todo items is done?

On Mon, 2022-12-05 at 15:59 +0900, Ian Lawrence Barwick wrote: > 2022年12月5日(月) 13:32 jian he : > > > > Hi, > > > > https://wiki.postgresql.org/wiki/Todo#Window_Functions > > > > > Implement full support for window framing clauses > > > > > > In addition to done clauses described in the latest d

Re: wiki postgresql Window_function some todo items is done?

2022年12月5日(月) 13:32 jian he : > > Hi, > > https://wiki.postgresql.org/wiki/Todo#Window_Functions > >> Implement full support for window framing clauses >> >> In addition to done clauses described in the latest doc, these clauses are >> not implemented yet. >> >> RANGE BETWEEN ... PRECEDING/FOLLOWI

wiki postgresql Window_function some todo items is done?

Hi, https://wiki.postgresql.org/wiki/Todo#Window_Functions Implement full support for window framing clauses In addition to done clauses described in the latest doc > , > these clauses are not implemen

Installing PostgreSQL 11 from source on Windows

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/index.html Description: I tried following the instructions on chapter 17 about the "Installation From Source Code on Windows" but they seem a bit confusing at practice when having to work

PostgreSQL source distribution files

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/tutorial-sql-intro.html Description: Section 2.1: https://www.postgresql.org/docs/current/tutorial-sql-intro.html "Examples in this manual can also be found in the PostgreSQL s

Re: PostgreSQL 15 minor documentation improvements

On Thu, Aug 18, 2022 at 12:46:41PM +0300, Maxim Yablokov wrote: > Yeah, sorry about that, I fixed it in the new patch. > As for the tag, it is written above: > pg_basebackup --target=shell > And also in backup.sgml there is the following: >  createdb -T template0 class="parameter">dbname > So I b

Re: PostgreSQL 15 minor documentation improvements

ckup.sgml index 56ac7b754be..a5f63bd6609 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -101,9 +101,7 @@ PostgreSQL documentation All WAL records required for the backup must contain sufficient full-page writes, - which requires you to ena

Re: PostgreSQL 15 minor documentation improvements

On Wed, Aug 17, 2022 at 06:09:13PM +0300, Максим Яблоков wrote: > I have prepared a small patch with possible changes of these places, and > also a separate patch with some improvements concerning missed/inapt tags. > Please have a look. archive_command is used only when archive_library is not set

PostgreSQL 15 minor documentation improvements

Hello! I’ve noticed that some changes concerning replacement of archive_command by archive_library in the documentation for PostgreSQL 15 do not quite fit in: 1. https://www.postgresql.org/docs/15/continuous-archiving.html Archiving of these files happens automatically since you have already

AW: PostgreSQL pdf shows 12.11 instead of 12.12

> > Hello % > > The PostgreSQL pdf (A4) shows 12.11 instead of 12.12 > > https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4 > .pdf > > >This link shows 12.12 for me. Perhaps you have some cache in your browser that >needs to be cleared? >//

Re: PostgreSQL pdf shows 12.11 instead of 12.12

On Tue, Aug 16, 2022 at 7:48 AM William Sescu (Suva) wrote: > > Hello % > > > > The PostgreSQL pdf (A4) shows 12.11 instead of 12.12 > > > > https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4.pdf > > This link shows 12.12 for me. Perhaps

PostgreSQL pdf shows 12.11 instead of 12.12

Hello % The PostgreSQL pdf (A4) shows 12.11 instead of 12.12 https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4.pdf However, the US doc looks correct. https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-US.pdf Cheers William

Re: PostgreSQL 15 minor fixes in protocol.sgml

an even directly say "commit prepared > transaction" but as you have written appears clear to me. > > * > For timestamp, related messages, we have three different messages: > Commit timestamp of the transaction. The value is in number of > microseconds since Postg

Re: PostgreSQL 15 minor fixes in protocol.sgml

ages, we have three different messages: Commit timestamp of the transaction. The value is in number of microseconds since PostgreSQL epoch (2000-01-01). Prepare timestamp of the transaction. The value is in number of microseconds since PostgreSQL epoch (2000-01-01). Rollback timestamp of the transacti

Re: PostgreSQL 15 minor fixes in protocol.sgml

On Tue, Aug 2, 2022 at 4:28 PM Michael Paquier wrote: > > On Mon, Aug 01, 2022 at 11:00:20PM +0300, Ekaterina Kiryanova wrote: > > > Another point worth mentioning is that only this file contains the phrase > > "two-phase transaction". I believe that "two-phase commit transaction" or > > "transact

Re: PostgreSQL 15 minor fixes in protocol.sgml

On Wed, Aug 3, 2022 at 1:58 PM Amit Kapila wrote: > > On Tue, Aug 2, 2022 at 4:28 PM Michael Paquier wrote: > > > > On Mon, Aug 01, 2022 at 11:00:20PM +0300, Ekaterina Kiryanova wrote: > > > > > Another point worth mentioning is that only this file contains the phrase > > > "two-phase transaction

Re: Dependency Tracking to be updated with PostgreSQL 14 functions on dependencies improvement.

On Wed, Jul 27, 2022, at 4:39 AM, PG Doc comments form wrote: > In PostgreSQL 14, we have added feature to check dependencies for function > defined with sql_body or language as SQL. > Reference :- > https://www.postgresql.org/docs/14/sql-createfunction.html > https://jkatz05.co

Re: PostgreSQL 15 minor fixes in protocol.sgml

On Mon, Aug 01, 2022 at 11:00:20PM +0300, Ekaterina Kiryanova wrote: > I didn't include it in the patch but I also suggest removing single quotes > around 'method' for the COMPRESSION option to help avoid confusion. (All the > supported compression methods consist of a single word so in my opinion

PostgreSQL 15 minor fixes in protocol.sgml

Hello! I've come across some typos in protocol.sgml for PostgreSQL 15 so please have a look at the attached patch. I didn't include it in the patch but I also suggest removing single quotes around 'method' for the COMPRESSION option to help avoid confusion. (All the s

Dependency Tracking to be updated with PostgreSQL 14 functions on dependencies improvement.

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/ddl-depend.html Description: In PostgreSQL 14, we have added feature to check dependencies for function defined with sql_body or language as SQL. Reference :- https://www.postgresql.org

Fwd: PostgreSQL 12 Authentication type questions

> Hello Postgresql Team, > > I have a question for you. > > If we would like to implement ldap authentication as well as password > authentication for some users at a same time (like authentication type as > password, global in oracle), Is there any option with postgres

Re: Minor language edits for PostgreSQL 14 Release Notes

On Tue, Jul 20, 2021 at 03:58:00PM +0300, Elena Indrupskaya wrote: > Hello everyone, > > I noticed minor language inaccuracies/inconsistencies in PostgreSQL 14 Release > Notes (https://www.postgresql.org/docs/14/release-14.html). A patch to fix > them > is attached. > On

Minor language edits for PostgreSQL 14 Release Notes

Hello everyone, I noticed minor language inaccuracies/inconsistencies in PostgreSQL 14 Release Notes (https://www.postgresql.org/docs/14/release-14.html). A patch to fix them is attached. One of the replacements changes "which reports WAL activity" to "to report WAL activit

Re: failed to connect to PostgreSQL server on "db01:5432" using INET socket

Hi, On 5/24/21 12:45 AM, Moin Akther wrote: > Dear Team, > >   > > We are getting below error logs from pgpool. > >   > > May 18 07:48:31 pgpool[22685]: [7-1] 2021-05-18 07:48:31: pid 22685: > LOG: failed to connect to PostgreSQL server on "db01:5432&q

failed to connect to PostgreSQL server on "db01:5432" using INET socket

Dear Team, We are getting below error logs from pgpool. May 18 07:48:31 pgpool[22685]: [7-1] 2021-05-18 07:48:31: pid 22685: LOG: failed to connect to PostgreSQL server on "db01:5432" using INET socket May 18 07:48:31 pgpool[22650]: 2021-05-18 07:48:31: pid 22685: LOG: failed to

Documentation for postgresql hooks

Hello, A couple years ago me and my friend created a repository with unofficial documentation for postgresql hooks <https://github.com/AmatanHead/psql-hooks/>. Since we don't really maintain it, I wonder if we could transfer ownership over it to someone who can take better care of

Re: On what system does the postgresql docs run?

On Wed, Nov 4, 2020 at 9:55 AM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/libpq-pgpass.html > Description: > > Hi, I really like the postgresql documentation system and am

On what system does the postgresql docs run?

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/libpq-pgpass.html Description: Hi, I really like the postgresql documentation system and am curious what it is. After viewing source and digging around, I can't seem to determine

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Sat, Aug 22, 2020 at 01:51:56PM -0400, Bruce Momjian wrote: > On Fri, Aug 21, 2020 at 08:41:54PM -0700, David G. Johnston wrote: > > On Fri, Aug 21, 2020 at 2:58 PM Bruce Momjian wrote: > > Good idea.  People have been confused about this before.  Attached is a > > patch. > > > > > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

> 26 Aug 2020, в 09:24, Николай Чадаев написал(а): > > Thank You Oleg. > > A simple example is extremely important and necessary. > I will wait for this example. It's already exists. The idea was to add cross links to this.

Re: Create a Foreign Table for PostgreSQL CSV Logs

e?I'll add: "on foreign table based on read only text file without indexes, etc". :) But in this case I indeed added some CHECK() constraints for old PostgreSQL and change them for the partition syntax sugar on new PostgreSQL to point on different files according to PostgreSQL defau

Re: PostgreSQL switchover process

without rebuilding a new standby i.e old > >> primary I want the replication happen b/w my new primary and > >> secondary. > > > > It may be many things without more information. Could you check > > pg_stat_replication on the primary and pg_stat_wal_receiver on t

Re: PostgreSQL switchover process

n on the primary and pg_stat_wal_receiver on the standby? Most likely something is wrong with primary_conninfo, but the logs of the standby should have enough information to let you know what happened. Another thing you are not telling is the version of PostgreSQL you are using here. In 12 and new

Re: PostgreSQL switchover process

mary and pg_stat_wal_receiver on the standby? Most likely something is wrong with primary_conninfo, but the logs of the standby should have enough information to let you know what happened. Another thing you are not telling is the version of PostgreSQL you are using here. In 12 and newer vers

PostgreSQL switchover process

Hi All, I'm trying to do the Switchover process in postgres. 1) I have my primary cluster running on port 5432 on server A 2) secondary cluster on the port 5432 on server B I did setup streaming replication b/w primary and secondary using replication slots. I did the following steps to perform s

Re: Create a Foreign Table for PostgreSQL CSV Logs

still not zero. Constraints are also >> a >> form of documentation. And also can be used (at least non-null ones) during >> optimization. > > I feel constraints are going to lose focus of what we are trying to > show. Do the constraints actually do anything on a foreign

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote: > On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote: > > There must not be constraints at all. Constraints are needed to check > incoming data to the table. But here table is read-only for database! > > > Please don't

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote: > There must not be constraints at all. Constraints are needed to check > incoming data to the table. But here table is read-only for database! > Please don't top-post. > So all your constraints is totally useless. > > > could become: > > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

There must not be constraints at all. Constraints are needed to check incoming data to the table. But here table is read-only for database! So all your constraints is totally useless. > > could become: > > > > connection_from text check(connection_from ~ '^[^:]+:[0-9]+$) -- the host > > and > >

Re: Minor fixes for PostgreSQL 13 documentation

On Sun, Aug 23, 2020 at 09:11:58PM +0900, Michael Paquier wrote: > I have looked again at the documentation and found just the five > places mentioned previously, giving the attached. And fixed with 77c1537, so we are done here. -- Michael signature.asc Description: PGP signature

Re: Minor fixes for PostgreSQL 13 documentation

On Sat, Aug 22, 2020 at 11:06:52AM -0400, Tom Lane wrote: > Michael Paquier writes: >> The docs of brin, gin, gist and spgist disagree with that. Wouldn't >> it be better to update all of them? > > Yeah, probably. See 47046763c for some policy I'd made up about when > to use --- typedef names

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Sat, Aug 22, 2020 at 10:51 AM Bruce Momjian wrote: > On Fri, Aug 21, 2020 at 08:41:54PM -0700, David G. Johnston wrote: > > Adding CHECK constraints and -- > > comments to the CREATE TABLE command would be a welcome addition. In > > particular I noticed: > > > > paragraph: client host:port nu

Re: Create a Foreign Table for PostgreSQL CSV Logs

diff --git a/doc/src/sgml/file-fdw.sgml b/doc/src/sgml/file-fdw.sgml index ed028e4ec9..c3e40f435c 100644 --- a/doc/src/sgml/file-fdw.sgml +++ b/doc/src/sgml/file-fdw.sgml @@ -215,7 +215,9 @@ One of the obvious uses for file_fdw is to make the PostgreSQL activity log available

Re: Minor fixes for PostgreSQL 13 documentation

Michael Paquier writes: > On Sat, Aug 22, 2020 at 01:10:11PM +0300, Alexander Lakhin wrote: >> - The function is passed a pointer to a >> local_relopts >> + The function is passed a pointer to a >> local_relopts > The docs of brin, gin, gist and spgist disagree with that. Wouldn't > it

Re: Minor fixes for PostgreSQL 13 documentation

On Sat, Aug 22, 2020 at 01:10:11PM +0300, Alexander Lakhin wrote: > Please consider applying fixes for bugs (incorrect tags, redundant > spaces, etc.) I noticed while translating the documentation. Thanks, Alexander. I have applied and back-patched most of it down to 13. > - The function is

Minor fixes for PostgreSQL 13 documentation

/datetime.sgml @@ -564,7 +564,7 @@ - PostgreSQL can accept time zone specifications that + PostgreSQL can accept time zone specifications that are written according to the POSIX standard's rules for the TZ environment variable. POSIX time zone specifications are @@ -

Re: Create a Foreign Table for PostgreSQL CSV Logs

.html > > Description: > > > > There is some imperfection in PostgreSQL doc. There are two section in > > documentation how to import PostgreSQL log into sql space and both not > > complete. One of them is: > > https://www.postgresql.org/docs/current/file-fdw.html &

Re: Create a Foreign Table for PostgreSQL CSV Logs

On Fri, Aug 21, 2020 at 09:25:20AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/runtime-config-logging.html > Description: > > There is some imperfection in PostgreSQL

Create a Foreign Table for PostgreSQL CSV Logs

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/runtime-config-logging.html Description: There is some imperfection in PostgreSQL doc. There are two section in documentation how to import PostgreSQL log into sql space and both not

Re: PostgreSQL 12: Cryptic documentation

"David G. Johnston" writes: > As with most things there is always room for improvement. In this case, > though, I'm not seeing anything wrong with the direct wording provided. Also, it's under a heading that says "The following command-line options control the location and format of the output",

Re: PostgreSQL 12: Cryptic documentation

On Sat, Aug 15, 2020 at 6:58 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/app-pgbasebackup.html > Description: > > The pg_basebackup page says that the --waldir parameter "Specifies the > location

PostgreSQL 12: Cryptic documentation

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/app-pgbasebackup.html Description: The pg_basebackup page says that the --waldir parameter "Specifies the location for the write-ahead log directory. waldir must be an absolute path. The w

Replication Binary in PostgreSQL 12

Hello, I am implementing binary replication in PostgreSQL 12. I have a lot of pending questions. Example, how to know a subscriber is up to date, if there is the possibility of knowing if the subscriber is currently connected to the publication, etc, etc. Where can I get more documentation?

Re: Developer FAQ / What information is available to learn PostgreSQL internals?

On 4/16/20 4:20 AM, Marc Rechté wrote: > > https://wiki.postgresql.org/wiki/Developer_FAQ > > This link is dead: introduction to Hacking PostgreSQL - With lots of > code review! > https://linux.org.au/conf/2007/att_data/Miniconfs(2f)PostgreSQL/attachments/hacking_intro.pdf

Developer FAQ / What information is available to learn PostgreSQL internals?

https://wiki.postgresql.org/wiki/Developer_FAQ This link is dead: introduction to Hacking PostgreSQL - With lots of code review! https://linux.org.au/conf/2007/att_data/Miniconfs(2f)PostgreSQL/attachments/hacking_intro.pdf

Re: recovery.conf in documentation for postgresql version 12

On Wed, 2020-04-08 at 07:31 +, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/10/pgarchivecleanup.html > Description: > > In various places of version 12 documentation, recovery.conf -file is > mentioned. > I thought that the file no longer existed in version 12? You were

recovery.conf in documentation for postgresql version 12

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/pgarchivecleanup.html Description: In various places of version 12 documentation, recovery.conf -file is mentioned. I thought that the file no longer existed in version 12? Yours truly Pe

Re: Spanish translation of postgresql manuals

On Wed, Jan 1, 2020 at 09:38:32PM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/index.html > Description: > > I am translating the Postgresql 10.11 manual into Spanis

Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes

On 09/01/2020 16:19, Peter Eisentraut wrote: > On 2020-01-03 11:00, Magnus Hagander wrote: >>     On 2019-12-30 00:03, Vik Fearing wrote: >> > Following a complaint on IRC about the dearth of information on >>     how to >> > migrate to a new major version in the release notes, the attach

  1   2   >