Transaction wraparound and read committed isolation level

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/routine-vacuuming.html Description: hey guys thanks for the work you do we really appreciate it. In the transaction wraparound section this statement is misleading and got me really con

Add missing meson arguments in docs

The -Dcassert and -Db_coverage of the meson build didn't show in the docs that they needed to be passed true or false. All other options specified the arguments they expected. This patch fixes that. 0001-Add-missing-meson-arguments-in-docs.patch Description: Binary data

Re: Transaction wraparound and read committed isolation level

On Sun, 2023-02-19 at 03:10 +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/routine-vacuuming.html > Description: > > hey guys > > thanks for the work you do we really appreciate it. > > In th

Re: February 9th, 2023 Release links to a missing page

On 2/20/23 8:57 PM, Kirk Wolak wrote: On Sun, Feb 19, 2023 at 4:55 PM Jonathan S. Katz Well, that gives me an idea. In the release announcement, we could put a line that says "You can send any corrections or suggestions to the public pgsql-...@lists.postgresql.org

MERGE examples not clear

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/sql-merge.html Description: On this page: https://www.postgresql.org/docs/15/sql-merge.html the first and second examples seems to be contrasted (by "this would be exactly equivalent to th

Re: MERGE examples not clear

On Tue, Feb 21, 2023 at 8:35 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sql-merge.html > Description: > > On this page: https://www.postgresql.org/docs/15/sql-merge.html > the first and second e

Re: Transaction wraparound and read committed isolation level

On Tue, Feb 21, 2023 at 1:51 AM Laurenz Albe wrote: > > If the current transaction isolation level is read committed it absolutely > > can see rows committed by future transactions with higher XIDs. > > You are right, in combination with PlanQualEval you can. You don't need to bring EvalPlanQual

Re: Transaction wraparound and read committed isolation level

On Tue, Feb 21, 2023 at 9:46 AM Peter Geoghegan wrote: > All that you need is two statements within the same READ COMMITTED > transaction, combined with a second concurrently executing > transaction. The second transaction need only start after the first > one (giving it a later XID), and then com

Row Level Security Execution within the SQL Evaluation Pipeline

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/sql-createpolicy.html Description: RLS documentation seems to say the user's predicate is evaluated AFTER the policy is evaluated. This presents to me an issue that I can't wrap my head ar

Re: Row Level Security Execution within the SQL Evaluation Pipeline

Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > RLS documentation seems to say the user's predicate is evaluated AFTER the > policy is evaluated. This presents to me an issue that I can't wrap my head > around, and seems to confuse others as well. > > Setup: > 1. We have a pol

Re: Add missing meson arguments in docs

On Tue, Feb 21, 2023 at 10:40:12AM +0100, Jelte Fennema wrote: > The -Dcassert and -Db_coverage of the meson build didn't show in the > docs that they needed to be passed true or false. All other options > specified the arguments they expected. This patch fixes that. Indeed, values have to be spec