On Monday, February 19, 2024, Johnathan Tiamoh
wrote:
>
> Please, I need help to fix this issue. I have increase client
> _idle_timeout from 15 minutes to 30 minutes and still facing the
> same problem.
>
>
Don’t connect through a pooler.
For a more helpful reply you need to actually show yo
Hello,
Please, I need help to fix this issue. I have increase client
_idle_timeout from 15 minutes to 30 minutes and still facing the
same problem.
Kind regards
Johnathan T.
Hello,
I need help to resolve the above issue.
Kind regards
Johnathan T.
Thank you very much @Adrian Klaver .
On Mon, Feb 19, 2024 at 2:45 PM Adrian Klaver
wrote:
> On 2/19/24 11:36, Johnathan Tiamoh wrote:
>
> Reply to list also.
> Cc'ing list.
>
> > Sorry Adrian,
> >
> > This is occurring at every checkpoint. This actually has to do with
> > Listen/Notify.
> > I
On Sun, Feb 18, 2024 at 10:32 PM Darryl Green
wrote:
> 1) Is my attempt to improve performance of insert AND (as the number of
> sources goes up, as it has) querying which is invariably by id but it is
> easy to include "and src = x" in the majority of usage (the other common
> case is to query a
ok, sorted it out. one of two things happened, either docker got
fussier about correct environment settings on the upgrade, or i
screwed up an edit of the environment file. i prefer to blame
docker rather than myself for obvious reasons...
richard
On Mon, 19 Feb 2024 17:00:10 -050
On Mon, 19 Feb 2024 at 22:07, Darryl Green wrote:
>
> On Mon, 19 Feb 2024 at 14:23, David Rowley wrote:
> >
> > On Mon, 19 Feb 2024 at 16:32, Darryl Green wrote:
> > > 2) It would be nice to be able to specify the id as pk on the table being
> > > partitioned (as it was in the non-partitioned d
Hello,
I have a Postgres database where many similar expression-based indexes have
been added by a script. It is quite likely that some of the indexes are not
actually used, and I would like to remove these unused indexes.
I can identify indexes that are used directly during query execution using
we're using Postgresql 14 with our Laravel/Php appliction. it is working well
in EC2 and in a Docker image on my Ubuntu 22.04 desktop at work. however,
a while back it stopped working with Docker on my Macbook Air in response
to a major OS upgrade. wondering if anyone knows what i might need to
On 2/19/24 11:36, Johnathan Tiamoh wrote:
Reply to list also.
Cc'ing list.
Sorry Adrian,
This is occurring at every checkpoint. This actually has to do with
Listen/Notify.
It is not really linked to the upgrade per say.
I would say it is.
From:
https://www.postgresql.org/docs/current/s
On 2/19/24 09:52, Zahir Lalani wrote:
Hi All
My understanding and hope was that Mat Views cache their data and that
is how they are so fast. But we are experience “cancelling statement due
to conflict with recovery” errors on MV’s with large data sets and I
thought that this could only happen
On Mon, Feb 19, 2024, 10:53 Zahir Lalani wrote:
> Hi All
>
>
>
> My understanding and hope was that Mat Views cache their data and that is
> how they are so fast. But we are experience “cancelling statement due to
> conflict with recovery” errors on MV’s with large data sets and I thought
> that
Hi All
My understanding and hope was that Mat Views cache their data and that is how
they are so fast. But we are experience "cancelling statement due to conflict
with recovery" errors on MV's with large data sets and I thought that this
could only happen if we ran the underlying query, not the
On 2/19/24 08:59, Johnathan Tiamoh wrote:
Hello,
Please, I need help in resolving this issue. I recently upgraded to
postgresql and have experienced the above error with 2 clusters already.
I keep losing data in the pg_exact directory.
We have been down this rabbit hole multiple times wi
Hello,
Please, I need help in resolving this issue. I recently upgraded to
postgresql and have experienced the above error with 2 clusters already.
I keep losing data in the pg_exact directory.
Kind regards
Johnathan T
On Monday, February 19, 2024, David G. Johnston
wrote:
> On Monday, February 19, 2024, Darryl Green wrote:
>
>>
>> > It may be possible to still have it work by doing a speculative record
>> > in the index for the target table then go and check all of the other
>> > indexes before marking the sp
On Monday, February 19, 2024, Darryl Green wrote:
>
> > It may be possible to still have it work by doing a speculative record
> > in the index for the target table then go and check all of the other
> > indexes before marking the speculative entry as valid.
>
> It is always valid - except in the
On 18.02.2024 15 :19, Dominique Devienne wrote:
...
...
But you of course can connect only to DBs you have explicit access to. Just
beware that before 15, the built-in PUBLIC
role, which all ROLEs are implicitly members of, had implicit access to newly
created DBs.
It's still the same c
On Mon, 19 Feb 2024 at 17:31, Peter Eisentraut wrote:
>
> On 19.02.24 04:32, Darryl Green wrote:
> > I note that in Postgresql 16 identity column handling in partitioned
> > tables has been aligned to the view that the partitioned table as a
> > whole is a single relation (and so a unique identity
On Mon, 19 Feb 2024 at 14:23, David Rowley wrote:
>
> On Mon, 19 Feb 2024 at 16:32, Darryl Green wrote:
> > 2) It would be nice to be able to specify the id as pk on the table
being partitioned (as it was in the non-partitioned definition of the
table) once to document and enforce that the partit
>
> 1) Is my attempt to improve performance of insert AND (as the number of
> sources goes up, as it has) querying which is invariably by id but it is
> easy to include "and src = x" in the majority of usage (the other common
> case is to query across all sources, asking for a set is unusual) a
> r
21 matches
Mail list logo
