Dear Shlok, Abrahim,
> Also, I was going to the logs on found:
> > > < 2025-07-08 14:57:08.653 UTC psql postgres postgres 172.18.0.94(53414)
> SELECT 0 2025-07-08 14:57:07 UTC 1096 686d31c3.448 2025-07-08
> 14:57:08.653 UTC > LOG: Initializing CDC decoder
>
> This log is not present in Postg
On Wed, Jul 9, 2025 at 1:02 PM Erik Johnston wrote:
> To recap: the situation is that, looking at our backup from 2025-06-26 via
> pageinspect, we have btree index rows which point to either non-existent heap
> TIDs, or to heap TIDs with data which does not correspond to the index row.
> In fac
On Wed, 2025-07-09 at 17:37 +0100, Mircea Cadariu wrote:
> Just to let you know that I have added a review through the commitfest app.
Thanks!
The patch is still in state "needs review".
If there is something that I should change, you should set it to
"waiting on author". If you think that the
> Best solution: Upgrade everyone to scram, then change md5 to scram in
> pg_hba.conf and never look back.
>
To expand more on the "upgrade everyone to scram", that means force all
users to set a new password while using scram (which should be the
default). You can do it yourself by getting a list
Hi again,
Thanks very much for the replies last week. We’ve been continuing to
investigate this problem, and I thought I’d share an update on where we are.
To recap: the situation is that, looking at our backup from 2025-06-26
via pageinspect, we have btree index rows which point to either
n
Hi Laurenz,
On 09/07/2025 16:26, Laurenz Albe wrote:
I have added the patch to the current commitfest:
https://commitfest.postgresql.org/patch/5871/
Just to let you know that I have added a review through the commitfest app.
You can see it here:
https://www.postgresql.org/message-id/flat/175
On 7/9/25 07:06, Jordan Adams wrote:
Hi Team,
Hope this email finds you well,
Apologies as I am unaware if this is the correct mailing address.
I would however like to inquire about an issue currently being
experienced with Postgres with one of our external clients.
When doing the setup and
On Wed, 2025-07-09 at 14:06 +, Jordan Adams wrote:
> "psql: FATAL: password authentication failed"
>
> Please advise if assistance can be provided?
Possibly. That error will cause an error message in the PostgreSQL
server log. Ask your DBA to find that error message and tell you
what it say
Hi Team,
Hope this email finds you well,
Apologies as I am unaware if this is the correct mailing address.
I would however like to inquire about an issue currently being experienced with
Postgres with one of our external clients.
When doing the setup and following the steps accordingly with re
On Wed, Jul 9, 2025 at 11:26 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wed, Jul 9, 2025 at 8:09 AM Ron Johnson
> wrote:
>
>> That requires setting the password to null and then recreating the
>> password, no?
>>
>
> You might want to verify that claim, and suggest a doc patch
On Wed, 2025-07-09 at 11:09 -0400, Ron Johnson wrote:
> > Best solution: Upgrade everyone to scram, then change md5 to scram
> > in pg_hba.conf and never look back.
>
> That requires setting the password to null and then recreating the
> password, no? Otherwise IIRC, changing an md5 password leav
On Wed, Jul 9, 2025 at 8:09 AM Ron Johnson wrote:
> That requires setting the password to null and then recreating the
> password, no?
>
You might want to verify that claim, and suggest a doc patch or bug fix if
you find it to be true - I sure don't see anything that remotely suggests
this.
Dav
On Wed, 2025-07-09 at 11:30 +, Zechman, Derek S wrote:
> > > There are no entries in pg_stats for the parent table until after I
> > > manually run an analyze on it – Example below
> >
> > You are right. I looked at the code, and "vacuumdb" does not process
> > partitiond tables, even if --an
On Wed, Jul 9, 2025 at 11:11 AM Adrian Klaver
wrote:
> On 7/9/25 06:56, Alpaslan AKDAĞ wrote:
> > Hello all
> >
>
> > As a result, some users are able to connect, while others cannot.
>
> What client is being used and what version of said client?
>
This is a salient point:clients from the pre-PG
On 7/9/25 06:56, Alpaslan AKDAĞ wrote:
Hello all
As a result, some users are able to connect, while others cannot.
What client is being used and what version of said client?
Best regards,
Alpaslan
--
Adrian Klaver
adrian.kla...@aklaver.com
On Wed, Jul 9, 2025 at 10:59 AM Greg Sabino Mullane
wrote:
> On Wed, Jul 9, 2025 at 9:57 AM Alpaslan AKDAĞ
> wrote:
>
>> Is it expected behavior that users created with scram-sha-256 passwords
>> can still connect via md5 in pg_hba.conf?
>
>
> Yes. From the docs:
>
>> To ease transition from the
On Wed, Jul 9, 2025 at 9:57 AM Alpaslan AKDAĞ
wrote:
> Is it expected behavior that users created with scram-sha-256 passwords
> can still connect via md5 in pg_hba.conf?
Yes. From the docs:
> To ease transition from the md5 method to the newer SCRAM method, if md5 is
> specified as a method i
On Wed, Jul 9, 2025 at 6:57 AM Alpaslan AKDAĞ
wrote:
>
>1. In such a case, what would be the recommended approach or best
>practice to follow during upgrades in order to avoid this kind of issue?
>
> This is all described quite clearly in the documentation, including the
upgrade procedure
Hello all
We have recently upgraded our PostgreSQL instances from version 13 to 16.
During the upgrade, we also changed the password_encryption setting in
postgresql.conf to scram-sha-256.
Before the upgrade, we used pg_dumpall --roles-only to export all users and
their MD5-hashed passwords. Afte
> > Well, that wouldn't explain why it doesn't work on partitioned tables.
> > I am under the impression that it should.
> >
> > Derek, can cou share the pg_stats entries for the partitioned table?
>
> There are no entries in pg_stats for the parent table until after I manually
> run an analy
On Wed, 9 Jul 2025 at 12:19, Shlok Kyal wrote:
>
> On Wed, 9 Jul 2025 at 11:43, abrahim abrahao wrote:
> >
> > 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 wor
21 matches
Mail list logo
