On 12.05.2021 05:42, Tom Lane wrote:
If you're in a position to apply the patch and see if it resolves
your real non-simplified case, that would be very helpful.
Also, this fix in principle will create a small performance
penalty for FOR-loops in non-atomic contexts such as DO loops.
It'd be int
Hi
it run into an issue with: ERROR: no known snapshots
It seems to me whenever I use a toasted value in a loop in plpgsql code
I get this error. Originally it happened in a procedure with a loop,
without a setting of and explicit storage on the column, eg. extended.
I can reproduce the erro
Hi,
I am confused, the documentation says for pg_stat_database
xact_commit Number of transactions in this database that have
been committed
and somewhere else
txid_current() get current transaction ID, assigning a new one
if the current transaction does not have one
I would ha
I may have misunderstood the documentation or your question, but I had
the understanding that xmin is not updated, but is only set on insert
(but yes, also for update, but updates are also inserts for Postgres as
updates are executed as delete/insert)
from https://www.postgresql.org/docs/10/ddl
Hi,
I think that the sql is not valid. Based on the order by documentation,
a column label cannot be used in an expression.
from https://www.postgresql.org/docs/11/queries-order.html
> Note that an output column name has to stand alone, that is, it
cannot be used in an expression.
R
I must have missed this, I did not immediately realize there was a
difference between select and delete
Thanks for the explanation and outlook.
Stefan
Hi,
I noticed that a delete on a table with many partitions seems to be
using a lot of ram.
It seems to occur during the planing phase, as explain behaves the same
as the actual execution of the delete.
On the simplified test below for 4000 partitions it seems to be using
for a short time o
