Hi,
Can you please provide the Pgpool logs? Additionally, in a distributed
environment, ensure that Pgpool is properly configured. You can follow
these documented steps to set up the Pgpool configurations
pgpool.conf,pcp.conf and pool_hba.conf .
Regards,
Muhammad Imtiaz
On Tue, 28 May 2024 at
Hi ,
You need to install the LLVM toolset.
1)Check that if it is installed or not :
yum list installed | grep llvm-toolset
2)If it is not installed, you can install it using the following command.
sudo yum install llvm-toolset-7
Regards,
Muhammad Imtiaz
On Wed, 29 May 2024 at 05:27, Ian
Alexander Staubo writes:
> (2) Set up schema. It's important to create the index before insertion, in
> order to provoke a
> situation where the indexes have dead tuples:
> ...
> (4) Then ensure all tuples are dead except one:
> DELETE FROM outbox_batches;
> INSERT INTO outbox_batches
2024年5月29日(水) 6:10 Sumit Kochar :
>
> Installation of Foreign data Wrapper on EDB Postgres to connect to SQL server
> database is not working.
>
>
>
> https://github.com/tds-fdw/tds_fdw/issues/357
>
>
>
> Please advise if this has been encountered or a workaround is available.
(...)
>
Installation of Foreign data Wrapper on EDB Postgres to connect to SQL server
database is not working.
https://github.com/tds-fdw/tds_fdw/issues/357
Please advise if this has been encountered or a workaround is available.
OS:
NAME="Oracle Linux Server"
VERSION="7.9"
ID="ol"
ID_LIKE="fedora"
On Mon, May 27, 2024 at 2:50 PM Laurenz Albe
wrote:
>
> > > But again for HA , in case primary down we should not be in big lag
> for the standby
> > > and thus we want the standby also with minimal lag. And as you
> mentioned there will
> > > never be incorrect results but at amx it will be
On 5/28/24 1:31 AM, vijay patil wrote:
HI Team,
"I'm encountering challenges while configuring Pgpool with high
availability. The initial setup is completed, and Pgpool is operational
on a single node, functioning without issues. However, upon attempting
to start Pgpool on any additional
Hi Christian:
On Tue, 28 May 2024 at 18:40, Christian Schröder
wrote:
> <2024-05-21 11:34:46 CEST - mailprocessor> ERROR: could not resize shared
> memory segment "/PostgreSQL.2448337832" to 182656 bytes: No space left on
> device
This hints at some shm function getting an ENOSPC: Coupled
Hi Vijay
Can you please share the error log, as from the description its hard to
figure out the issue causing this problem.
Regards
Kashif Zeeshan
Bitnine Global
On Tue, May 28, 2024 at 9:42 PM vijay patil
wrote:
>
> HI Team,
>
> "I'm encountering challenges while configuring Pgpool with high
HI Team,
"I'm encountering challenges while configuring Pgpool with high
availability. The initial setup is completed, and Pgpool is operational on
a single node, functioning without issues. However, upon attempting to
start Pgpool on any additional nodes, particularly node 2, it becomes
Hi all,
We migrated from PostgreSQL 9.4 to PostgreSQL 15 a while ago. Since then, we
have a lot of memory issues in our QA environment (which is a bit tense in
resources). We did not have these problems before the migration, and we do not
have them in our production environment, which has a lot
On Tue, May 28, 2024, 07:21 Alexander Staubo wrote:
>
>
> I did explore a solution which is my “plan B” — adding a “done” column,
> then using “UPDATE … SET done = true” rather than deleting the rows. This
> causes dead tuples, of course, but then adding a new index with a “… WHERE
> NOT done”
On 28 May 2024, at 13:02, Laurenz Albe wrote:
> ANALYZE considers only the live rows, so PostgreSQL knows that the query will
> return only few results. So it chooses the smaller index rather than the one
> that matches the WHERE condition perfectly.
>
> Unfortunately, it has to wade through
On Tue, 2024-05-28 at 10:00 +0200, Alexander Staubo wrote:
> I am encountering an odd problem where Postgres will use the wrong index,
> particularly if the table
> has some dead tuples. The database affected is running 12.6, but I can also
> reproduce with 16.3.
>
> To reproduce:
> [create a
I am encountering an odd problem where Postgres will use the wrong index,
particularly if the table
has some dead tuples. The database affected is running 12.6, but I can also
reproduce with 16.3.
To reproduce:
(1) Disable autovacuum. This is just so we can induce a scenario where there
are
På tirsdag 28. mai 2024 kl. 01:48:17, skrev Tom Lane mailto:t...@sss.pgh.pa.us>>:
Laurenz Albe writes:
> On Mon, 2024-05-27 at 09:33 +0200, Andreas Joseph Krogh wrote:
>> I tried:
>> REVOKE SELECT ON pg_catalog.pg_database FROM public;
>> But that doesn't prevent a normal user from querying
16 matches
Mail list logo
