time dates - Search results in mailing lists

2025-05-19 06:32:44 | pgsql: Doc: add pre-branch task to run src/tools/copyright.pl. (Tom Lane)

date to sneak into the tree between early January (when we normally run copyright.pl) and feature freeze. Immediately before branching the new release is an ideal time

2025-03-14 11:24:35 | pgsql: Respect changing pin limits in read_stream.c. (Thomas Munro)

time due to pins acquired outside this stream by the same backend. No extra CPU cycles are added to the all-buffered fast-path code, but the I/O-starting path now considers the up-to-date

2024-12-24 13:59:40 | pgsql: Remove pgrminclude annotations (Peter Eisentraut)

time someone tried to do something with pgrminclude was around 2011. Many (not all) of the "pgrminclude ignore" annotations are of a newer date

2024-12-23 23:14:41 | pgsql: postgres_fdw: re-issue cancel requests a few times if necessary. (Tom Lane)

time, for the remote query to start; but now we're intentionally risking the race condition occurring sometimes in the buildfarm, so that the repeat-cancel code path will get some testing. As before, back

2024-12-23 23:14:41 | pgsql: postgres_fdw: re-issue cancel requests a few times if necessary. (Tom Lane)

time, for the remote query to start; but now we're intentionally risking the race condition occurring sometimes in the buildfarm, so that the repeat-cancel code path will get some testing. As before, back

2024-05-09 22:56:56 | pgsql: Doc: update the "Using EXPLAIN" examples to match current code. (Tom Lane)

date in that we show more numbers than we did at the time. Possibly chapter

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-04-04 19:32:09 | [MASSMAIL] pgsql: Fix ecpg's mechanism for detecting unsupported cases in the gram (Tom Lane)

dating to 2008 to suppress the warning in one rule that doesn't even exist anymore, but nothing for other cases we've created since then. End result was that you could get "unsupported feature

2024-02-27 08:37:15 | pgsql: Rationalize and improve error messages for some jsonpath items (Andrew Dunstan)

date-time types are unified and parameterized, instead of using a fully separate error message

2024-02-20 19:35:29 | pgsql: Doc: improve explanation of type interval, especially extract(). (Tom Lane)

date for a very long time. Also, it was mostly silent about how interval inputs

2024-02-20 19:35:29 | pgsql: Doc: improve explanation of type interval, especially extract(). (Tom Lane)

date for a very long time. Also, it was mostly silent about how interval inputs