public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dominique Devienne <[email protected]>
To: Ron Johnson <[email protected]>
Cc: [email protected]
Subject: Re: Latest patches break one of our unit-test, related to RLS
Date: Fri, 5 Sep 2025 10:19:04 +0200
Message-ID: <CAFCRh-9n5RsGoJWXFqmqmOKxfA0WWQCVBt9gSMnyPz3G5DzCvg@mail.gmail.com> (raw)
In-Reply-To: <CANzqJaDbA1v95Dj+x7x_VXkxcfPY7SAMdVX7ADFAeZw8HQ0Diw@mail.gmail.com>
References: <CAFCRh-8NwJd0jq6P=R3qhHyqU7hw0BTor3W0SvUcii24et+zAw@mail.gmail.com>
	<CANzqJaDbA1v95Dj+x7x_VXkxcfPY7SAMdVX7ADFAeZw8HQ0Diw@mail.gmail.com>

On Fri, Sep 5, 2025 at 1:10 AM Ron Johnson <[email protected]> wrote:
> Dumb question: did you read the release notes?

Well, now I have. Carefully. Nothing stands out.
There's RLS mentioned, but for indexing only.
So no smoking gun. We'll have to investigate... :(

> In our case, 17.6 "pg_dump --schema-only" broke in the sense that the md5sum of yesterday's schema dump is different from today's schema dump.  Puzzled, I ran "pg_dump --schema-only" twice in a row, but the md5sum was different.
> "diff" showed why.  Searching the release notes showed me what changed.

Thanks for the heads up.
We don't depend on pg_dump at all.
We have our own COPY BINARY based custom backup/restore
to semi-structured SQLite DBs (part relational, part per-row COPY blobs).

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Latest patches break one of our unit-test, related to RLS
  In-Reply-To: <CAFCRh-9n5RsGoJWXFqmqmOKxfA0WWQCVBt9gSMnyPz3G5DzCvg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox