On 12/16/19 9:46 AM, Sar wrote:
Hi,
I have database on Windows Server, running postgresql 10 and I've run
pg_dump with options: -Fc --verbose -d db_name --file "E:\backup.sql"
-T some_table.
Now when I run pg_restore, also on windows server with postgresql 12, or
on the same original server w
Hi,
I have database on Windows Server, running postgresql 10 and I've run pg_
dump with options: -Fc --verbose -d db_name --file "E:\backup.sql" -T some_
table.
Now when I run pg_restore, also on windows server with postgresql 12, or on
the same original server with postgresql 10, using option
It looks like you are creating a partition for each minute of the day (when
logs get inserted for a given minute at least). Would it be at all
reasonable to have an hourly or daily job which creates the partitions
ahead of when they are actually needed? If partitions went unused in the
recent past,
Hi Andrei
General speaking any DDL (Create, Alter Drop .etc) commands issue
exclusive locks automatically, so anything this transaction touches starts
getting exclusive locks. Assuming this is a multi-threading app these two
threads are sending commands all but at the same time. The Exclusive
Hi, Justin
I’ve managed to reproduce this deadlock (different threads) and it looks it
happens while Postgres tries to insert data into unique index for pg_type table
(it creates a new row-type for every new table and a new partition is a new
table). 16453 is old of the parent's table for the p
Hi Andrei,
My gut reactions is Yes this is a deadlock caused by a race condition, the
error from psycopg2 tells us that. Question becomes what is causing these
two process to collide, are both processes 33 and 37 python code, As both
are trying to access the same resource 16453 i would assume
## Daulat Ram (daulat@exponential.com):
> Can you please describe the
> " =Tc/postgres + postgres=CTc/postgres +confluence=CTc/postgres".
It's all here:
https://www.postgresql.org/docs/current/ddl-priv.html
Regards,
Christoph
--
Spare Space
Le lundi 16 décembre 2019 à 11:13:10 UTC+1, Luca Ferrari
a écrit :
On Mon, Oct 7, 2019 at 10:12 PM Bruce Momjian wrote:
> Do the Postgres docs need improvement here?
I don't know, but I would probably add a flag column in the firing
matrix to indicate when the related function will return a n
I think that I’ve got a deadlock (which is handled by `exception when others`
statements). But the problem is it occurs too fast. Is it possible to get a
deadlock faster than deadlock_timeout? It’s set to 1s (default value) but it
looks like I get it immidiately. Error message I’m getting after
Hello,
Can you please describe the " =Tc/postgres + postgres=CTc/postgres
+confluence=CTc/postgres". I want to give the same permissions to the
different user on a new database.
List of databases
Name| Owner | Encoding | Collate | Ctype |Access
Hello!
pg_probackup can do that:
https://postgrespro.github.io/pg_probackup/#pbk-partial-restore
On 12/15/19 5:32 PM, Abraham, Danny wrote:
I assume that this magic does not exist.
Am I right ?
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Compan
11 matches
Mail list logo