iew in the Introduction to Locking section.
I don't know exactly which section you mean, but it should definitely
be part of the tutorial, in chapter 3.4.
Appendix J contains some information about building the documentation
from source. The patch should be against the current developm
update]
>
> The problem is that this fundamental problem is lost in all the escoteric
> details of locking.
>
> Sure, a database expert that carefully studies the docs might figure it
> out if they did not already know it. But the other 99.9% of users will
> just consider Postgr
On Thu, 2024-03-14 at 00:16 +, PG Doc comments form wrote:
> There really needs to be an explicit warning that the following is invalid
> in normal read committed mode:-
>
> select foo into f from bar where id=1;
> f = f + 123;
> update bar set foo = f where id =1;
> commit;
>
> This is a ver
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/mvcc-intro.html
Description:
There really needs to be an explicit warning that the following is invalid
in normal read committed mode:-
select foo into f from bar where id=1;
f = f + 123;
On 08.09.21 18:37, Tom Lane wrote:
PG Doc comments form writes:
The docs mention "For example, a common use of advisory locks is to emulate
pessimistic locking strategies typical of so-called “flat file” data
management systems" which is exactly what I wanted to use to port some
PG Doc comments form writes:
> The docs mention "For example, a common use of advisory locks is to emulate
> pessimistic locking strategies typical of so-called “flat file” data
> management systems" which is exactly what I wanted to use to port some code
> from using SQLi
ory locks is to emulate
> pessimistic locking strategies typical of so-called “flat file” data
> management systems" which is exactly what I wanted to use to port some code
> from using SQLite to using PostgreSQL. (The code in question requires
> serializable transactions and c
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/explicit-locking.html
Description:
The docs mention "For example, a common use of advisory locks is to emulate
pessimistic locking strategies typical of so-called “flat file”
ETAIL: Key (id1)=(1) already exists.
Which is what I would expect from both tables.
At a minimum, index locking order should be documented and explained.
It may also be desirable to have a configuration option to switch the index
locking order to alphabetical by name to make it easy to control like
triggers.
On 2019-Jun-14, Pavel Luzanov wrote:
> Does it make sense to change this way?
> "Some operations require a stronger lock when using declarative partitioning
> than when using table inheritance. For example, removing a
> partition from a partitioned table requires taking an ACCESS EXCLUSIVE
> lock
On 13.06.2019 23:07, Alvaro Herrera wrote:
On 2019-Jun-13, Pavel Luzanov wrote:
Hello,
According to patch[1] and after playing with v12 beta1 I think that this
item can be dropped from "5.11.3. Implementation Using Inheritance" section
of v12 docs:
"Some operations require a stronger lock w
On 2019-Jun-13, Pavel Luzanov wrote:
> Hello,
>
> According to patch[1] and after playing with v12 beta1 I think that this
> item can be dropped from "5.11.3. Implementation Using Inheritance" section
> of v12 docs:
>
> "Some operations require a stronger lock when using declarative partitioning
Hello,
According to patch[1] and after playing with v12 beta1 I think that this
item can be dropped from "5.11.3. Implementation Using Inheritance"
section of v12 docs:
"Some operations require a stronger lock when using declarative
partitioning than when using table inheritance. For example
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-reindex.html
Description:
Paragraph in question:
REINDEX is similar to a drop and recreate of the index in that the index
contents are rebuilt from scratch. However, the locking
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-reindex.html
Description:
Paragraph in question:
REINDEX is similar to a drop and recreate of the index in that the index
contents are rebuilt from scratch. However, the locking
15 matches
Mail list logo
