time dates - Search results in mailing lists
Mailing lists >> pgsql-docs >> Thread
2024-11-05 21:41:33 | Re: Serializable Transaction Anomoly (Daniel Bickler)
Date: Tuesday, November 5, 2024 at 12:21 PM
To: Daniel Bickler
Mailing lists >> pgsql-docs >> Thread
2024-07-17 01:20:49 | Re: Re: Mismatch for connection key/value pair between documentation and code? (周志勤)
Date: 2024-07-16 22:20
To: joe.zhou@dualhelios.com; pgsql-docs@lists.postgresql.org
Subject: Re: Mismatch for connection key/value pair between documentation and code?
On Monday, July 15, 2024, PG Doc comments form
Mailing lists >> pgsql-docs >> Thread
2023-12-09 16:29:00 | Re: unclear wording re: spoofing prevention on network connections (Bruce Momjian)
Date: Wed Apr 3 15:02:33 2019 -0400 GSSAPI encryption support On both the frontend and backend, prepare for GSSAPI encryption support by moving common code for error handling into a separate file
Mailing lists >> pgsql-docs >> Thread >> Search in thread (4)
2023-11-22 13:02:02 | Re: [DOCS] Add example about date ISO format (Erik Wienhold)
On 2023-11-22 10:14 +0100, Laurenz Albe wrote: This might be excessive, but
Mailing lists >> pgsql-docs >> Thread >> Search in thread (16)
2023-11-11 22:45:04 | T is a mandatory date time separator in RFC3339 but documentation states differently (PG Doc comments form)
date+time values. Just for clarity's sake, this is stated in the section 5.5: This
Mailing lists >> pgsql-docs >> Thread
2023-10-10 05:32:12 | Setting up WAL archiving (PG Doc comments form)
date and time of the creation of the WAL. In case of restore, when WAL are not on disk
Mailing lists >> pgsql-docs >> Thread
2023-09-19 12:48:32 | SSI retry strategy (PG Doc comments form)
dates (select), insert a new reservation if it is and throw a business exception otherwise. However, sometime the error is thrown when insert is executed. The message is still "could not serialize access
Mailing lists >> pgsql-docs >> Thread
2023-08-11 00:23:45 | Re: Include PostgresNIO Swift client in the Documentation (Jonathan S. Katz)
time this came up, I think we discussed linking to the wiki page from the docs, vs. trying to keep the docs up-to-date
Mailing lists >> pgsql-docs >> Thread
2023-08-10 16:05:55 | PG 16 New Feature --“Accept the spelling "+infinity" in datetime input ”is not accurate (yanliang lei)
time zone 3.date and the spelling "+infinity" can not be used in the following
Mailing lists >> pgsql-docs >> Thread
2023-07-18 18:14:10 | Re: IN for records (Tom Lane)
date. As for the other one, I have no idea what it's even talking about: we do resolve all the comparison operators at parse time
Mailing lists >> pgsql-docs >> Thread
2023-05-19 18:03:43 | Incorrect/confusing information about timetz (PG Doc comments form)
dates and times are stored internally in UTC. They are converted to local time in the zone
Mailing lists >> pgsql-docs >> Thread
2022-12-05 06:59:59 | Re: wiki postgresql Window_function some todo items is done? (Ian Lawrence Barwick)
date. The emails it links to are all from 2008, which is around the time
Mailing lists >> pgsql-docs >> Thread
2022-08-04 15:14:53 | Re: The sample FDW table: pglog not work in https:///docs/14/file-fdw.html (Xiong He)
Date: Thu, Aug 4, 2022 04:09 PM
To: "Xiong He"
Mailing lists >> pgsql-docs >> Thread >> Search in thread (3)
2022-01-27 16:41:35 | RE: Datetime formatting (Kruus, Robert SPSA)
date and time. PostgreSQL accepts that format on input, but on output it uses a space
Mailing lists >> pgsql-docs >> Thread
2021-12-19 21:08:09 | The pg_stop_backup will return one row with three values. (PG Doc comments form)
date. pg_stop_backup --------------------------------------------------------------------------- (0/2000138,"START WAL LOCATION: 0/2000028 (file 000000010000000000000002)+ CHECKPOINT LOCATION: 0/2000060 + BACKUP METHOD: streamed + BACKUP FROM: primary + START TIME