I am using timescaledb version 2.7.2, and PostgreSQL 12.11 (Ubuntu
12.11-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
I tried to compress a chuck using the compress_chunk function and running a job
as well, and I got "sequence id overf
There is a three-day vacuum freeze on a partition table with wait_event =
BufferPin, no transactions (active or idle) older than it that are not blocked,
but at least one select query is executing at all times related of this
partition table.
This behaviour happens with some partitions, but n
2 20:01:26.429547+00 | SELECT 54002 |
AccessShareLock | 2024-02-02 20:01:32.749586+00 | SELECT 53583 |
AccessShareLock | 2024-02-02 20:01:34.624046+00 | SELECT
On Friday, February 2, 2024 at 01:37:19 p.m. EST, Greg Sabino Mullane
wrote:
On Wed, Jan 31, 2024 at 2:0
Thanks again Greg, I really appreciated all information.
On Friday, February 2, 2024 at 08:16:41 p.m. EST, Greg Sabino Mullane
wrote:
On Fri, Feb 2, 2024 at 3:25 PM abrahim abrahao wrote:
SHARE UPDATE EXCLUSIVE (ShareUpdateExclusiveLock) should not be blocked by
ACCESS SHARE
I got error “server process was terminated by signal 11: Segmentation fault”
using pg_create_logical_replication_slot with pgoutput plugin parameter and
using test_decoding worked fine, any idea that is wrong?
Note: I am using docker container and I also updated shm-size from 1024mb to 2g
and I
Thanks Hayato and Shlok, The Citus extension package is installed, but it is
not preload on shared_preload_libraries and citus extesion is not created.I
will create a new container without Citus extension package and adding stack
trace ( I think this is the one you're talking about) as soon as
Hi Hayato and Shlok, I confirmed that it is related of Citus, everytrhing
worked after remove the Citus instalation from the docker image.
I did not added stack trace yet on the new instalation. It seems that the
present Citus installation was done in an unusual way. I will work to figure
out a
