Hi,
We are using PostgreSQL 9.3.11. We are observing DB update failed due to
lock timeout. failure because waiting for RowExclusiveLock. Autovacuum uses
plain vacuum which uses ShareUpdateExclusiveLock. right?
But from Postgres Manual chapter 13.3. Explicit Locking. both Locks has no
conflict. S
Hi,
Thank you very much. It help us a lot
--
View this message in context:
http://postgresql.nabble.com/Doesn-t-PostgreSQL-clean-data-in-data-file-after-delete-records-from-table-tp5894764p5894960.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql
Hi,
we are using PostgreSQL 9.3.6 version and observe data file size is not
decreased after we deleted records from the table. It looks quite abnormal.
Is it as PostreSQL designed?
DBTestPostgres=# select count (*) from test_data ;
0
# ls -l
total 788932
.
-rw--- 1 _nokfss
Hi,
Thank you. This was designed storage solution deployed in cloud among with
other storage usage. We will remove glusterfs solution to DB usage. We don't
intend to use glusterfs to do data replication. But PostgreSQL may think
about variable storage solutions.
--
View this message in contex
Hi,
Thank you for the advice.This was designed storage solution deployed in
cloud among with other storage usage. We will remove glusterfs solution to
DB usage.
--
View this message in context:
http://postgresql.nabble.com/Does-PostgreSQL-support-to-write-glusterfs-by-Libgfapi-tp5877793p58784
Hi,
It seems low performance PostgreSQL(9.3.6) while writing data to glusterFS
distributed file system. libgfapi is provide since GlusterFS version 3.4 to
avoid kernel visits/data copy which can improve its performance. But I
didn't find out any instruction from the PostgreSQL web page. Do you kn
Hi,
Per my understanding, From the query which resulted in the deadlock
“SELECT sequence_name, start_value, increment_by***”, it appears
that the query which holds the lock is related to sequence numbers. From our
understanding it appears that, whenever there is a serial type of data
mem
Unfortunately what's the process 2720 is unknown as no any else log to
indicate it. It might because the debug level of PostgreSQL had been set too
lower to show more.
--
View this message in context:
http://postgresql.nabble.com/pg-restore-encounter-deadlock-since-PostgreSQL-bringing-up-tp5874
Hi,
pg_restore is executed by our own process actually, before that, our
process connects the data base via ODBC to access database template1 see if
PostgreSQL server is up. But pg_restore still failed after connect database
I understand the result is same as pg_ctrl output, is that true? Thank
Hi,
While start PostgreSQL(9.3.6) and execute pg_restore soon after PostgreSQL
bringing up. I encounter pg_restore failure because of deadlock detected.
postgres[2737]: [3-1] LOG: process 2737 detected deadlock while waiting for
AccessExclusiveLock on relation 7 of database 24577 after 1000.
10 matches
Mail list logo