On Thu, Mar 6, 2025 at 10:38 AM Ron Johnson wrote:
> This statement runs great from the psql prompt. Does exactly what I want.
> select datname from pg_database WHERE datname !~ 'template|postgres' ORDER BY
> datname;
>
> But it doesn't work so well from the bash prompt. Not escaping the "!"
>
On Fri, Feb 21, 2025 at 3:33 PM Tom Lane wrote:
> Dominique Devienne writes:
> > The point I'm trying to make, is that "hunting down" grantor(s) to
> connect
> > to DB(s) to be able to "force drop" a ROLE is a PITA. And I really wish
> > t
On Fri, Feb 21, 2025 at 3:45 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Friday, February 21, 2025, Dominique Devienne
> wrote:
>
>> On Fri, Feb 21, 2025 at 3:33 PM Tom Lane wrote:
>>
>>> Dominique Devienne writes:
>>> > The
On Thu, Feb 20, 2025 at 5:52 PM Tom Lane wrote:
> So grants and revokes are still being done as the object owner by
> default.
>
> Now I'm unclear on exactly what was happening in Dominique's case.
> Was the problematic permission granted by somebody other than the
> database's owner?
>
Here's m
On Thu, Feb 20, 2025 at 4:27 PM Tom Lane wrote:
> Dominique Devienne writes:
> > Error: DDL Error: GRANT USAGE ON SCHEMA "SCH1", "SCH2" TO "SCH2:RO",
> > "SCH2:RW", "SCH2:SU": #XX000: ERROR: tuple concurrently updated
>
> S
Hi,
We have a few dozen queries involving grandparent, parent, child table
triplets,
to implement a pre-existing API on top of PostgreSQL. That API is not
SQL-based
nor SQL "friendly" either, that's why we detect patterns in the APIs
inputs, to use
different SQL queries, as (important) optimizatio
On Mon, Feb 24, 2025 at 12:33 PM Matthias Apitz
wrote:
> Thanks for your hint, Jeremy. But this does not work either:
>
> postgres=# SELECT collname, collversion FROM pg_collation where collname =
> 'de_DE.utf8';
> collname | collversion
> +-
> de_DE.utf8 | 2.38
> (1 r
On Mon, Feb 24, 2025 at 3:51 PM Rob Sargent wrote:
> API:
> > * The first type never relies on fuzzy-find.
>
> Then have that app type use the simple, fast query.
>
I'm sorry, but that's neither helpful, nor relevant. --DD
On Mon, Feb 24, 2025 at 5:39 PM Greg Sabino Mullane
wrote:
> On Mon, Feb 24, 2025 at 4:46 AM Dominique Devienne
> wrote:
>
>> But now we have a new requirement, for "fuzzy find". I.e. the client can
>> ask for names
>> which are not the exact in-DB n
On Thu, Feb 20, 2025 at 3:31 PM Ron Johnson wrote:
> On Thu, Feb 20, 2025 at 8:07 AM Dominique Devienne
> wrote:
>
>> Hi. I've just read
>> https://www.dbi-services.com/blog/postgresql-18-virtual-generated-columns/
>>
>> and I'm wondering whether t
Hi. A tester just tried to restore two custom backups (not official
PostgreSQL ones) concurrently.
The restore process creates a new schema, some roles,and does some
role-to-role grants, before loading the data.
The two restores are independent, i.e. create different non-overlapping
schemas.
But b
On Thu, Feb 20, 2025 at 4:27 PM Tom Lane wrote:
> Dominique Devienne writes:
> > Hi. A tester just tried to restore two custom backups (not official
> > PostgreSQL ones) concurrently.
> > ...
> > The second session completed OK.
> > But the first session errors
Hi. Today I was surprised that REVOKE ALL ON DATABASE FROM ROLE silently
did nothing, even with CASCADE, when I was running it as SUPERUSER,
preventing DROP'ing the ROLE. I had to manually SET ROLE to the GRANTOR, do
the REVOKE, which DID something this time, and then I could DROP the role.
That's
On Thu, Feb 20, 2025 at 5:05 PM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Thursday, February 20, 2025, Dominique Devienne
> > wrote:
> >> Hi. Today I was surprised that REVOKE ALL ON DATABASE FROM ROLE silently
> >> did nothing, even with
Hi. I've just read
https://www.dbi-services.com/blog/postgresql-18-virtual-generated-columns/
and I'm wondering whether there will be a way to ALTER existing STORED
generated columns, to be virtual? W/o rewriting the whole table that is.
Thanks, --DD
On Thu, Mar 20, 2025 at 4:43 PM Sebastien Flaesch
wrote:
> OR ( I guess I start to understand the code... ) it this comment only for:
> #define CASHOID MONEYOID
> #define LSNOID PG_LSNOID
That's what Tom already replied, yes. --DD
On Thu, Jun 5, 2025 at 11:07 AM Dominique Devienne wrote:
> So... It is possible to have the SAME command on Windows and Linux,
> which yields the SAME datcollate and datctype values???
> So far, such a command eludes me, I'm afraid. --DD
So I tried to be explicit about lc_collat
Hi. Little mystery we don't understand. v17.
Create new DB, owned by dedicated new ROLE.
Create extension (pgcrypto) in our case. Installed in public, owned by
DB owner role.
Create schemas and populate them inside the DB.
This also creates roles associated to those schemas.
One of the schema is o
On Thu, Jun 19, 2025 at 4:18 PM Adrian Klaver wrote:
> On 6/19/25 06:09, Dominique Devienne wrote:
> > Hi. Little mystery we don't understand. v17.
> Does 'all' include the public schema?
No. We don't touch `public` at all, beside pgcrypto ending up inside it.
On Thu, Jun 19, 2025 at 6:35 PM Laurenz Albe wrote:
>
> On Thu, 2025-06-19 at 15:09 +0200, Dominique Devienne wrote:
> > Hi. Little mystery we don't understand. v17.
> > We're stumped for now.
>
> So are we. Why do you keep us guessing instead of posting a repro
On Thu, Jun 5, 2025 at 2:40 PM Daniel Verite wrote:
> Dominique Devienne wrote:
> > On Linux, no error unlike on Windows (still inconsistent there IMHO),
> > but the result is slightly different for datcollate and datctype (C vs
> > en_US),
> > while the
On Thu, Jun 5, 2025 at 5:01 PM Daniel Verite wrote:
> Dominique Devienne wrote:
> > > locale 'C.UTF-8' or lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8'
> > > cannot work on Windows because Windows does not have a locale
> > > name
On Thu, Jun 5, 2025 at 1:06 AM Tom Lane wrote:
> > Provide a client connection option (and/or implement the backend support)
> > to allow only one statement in an execute request
>
> This exists already; you just have to use the extended query protocol.
Hi Tom. Can you be more specific please?
I
On Wed, Jun 26, 2024 at 2:25 PM Dominique Devienne wrote:
> On Wed, Jun 26, 2024 at 11:08 AM Laurenz Albe
> wrote:
> > On Wed, 2024-06-26 at 10:35 +0200, Dominique Devienne wrote:
> > > So I have two questions:
> > > 1) Is there any way to know the current_role of
Hi.
For a long time, I was just doing a plain CREATE DATABASE, using
whatever local template1 was using.
Then when v17 came out, I wanted to force UTF-8 for the encoding,
*AND* use the new C.UTF-8 builtin locale, to not depend on libc on
Linux. (which forced me to use template0 explicitly). And s
Hi. I decided to test our stuff against the v18 beta1.
And right off the bat, I'm getting differences when introspecting a
schema via the catalogs, which now return NOT NULL constraints for
regular columns, which was not the case before, and when the doc seems
to say pg_constraint.contype = n is f
On Wed, Jun 4, 2025 at 3:07 PM Dominique Devienne wrote:
> Is this change of behavior normal?
> ... Was this intentional?
Well, apparently it is intentional, I found an entry in the release notes.
Case closed I guess. I adapted our introspection. Thanks, --DD
>From https://www.postg
(Robert, you were kind enough to help me understand the v16 changes,
so I'm hoping you might have insight on this too. And this time
around, it's not one year too late I hope, since I'm testing betas
now. See
https://www.postgresql.org/message-id/CA%2BTgmoZMqsg6-6qN_fuMZTGu%3DVdyjv-u9ZgWbEnOTvRE45
On Wed, Jun 4, 2025 at 4:25 PM Robert Haas wrote:
> Hi Dominique,
Hi Rober,
> Thanks for testing. This time, whatever is going wrong here is
> probably not my fault, because I don't think I changed anything in
> this area for v18. Actually, I'm unaware of anyone else having made
> significant ch
On Wed, Jun 4, 2025 at 5:29 PM Adrian Klaver wrote:
> > $ ./myruntests.csh tests_pdgm_schemas -t "..." --pq-version
> > Connected to ... (17.4, server 18.0)
>
> What is '(17.4, server 18.0)' referring to?
>
> What is the actual test being run below?
17.4 is the client-side version, i.e. the LibPQ
On Wed, Jun 4, 2025 at 5:34 PM Tom Lane wrote:
> Dominique Devienne writes:
> > In any case, if anyone else knows about changes in this area, I'm
> > interested.
>
> Digging through the commit log didn't find much, but conceivably
>
> https://git.post
On Thu, Jun 5, 2025 at 3:01 AM Laurenz Albe wrote:
> On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote:
> > The command I'm using (from a libpq trace) is:
> >
> > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8'
>
On Thu, Jun 5, 2025 at 4:52 AM Jeff Davis wrote:
> > On Windows, I'm getting
> I tried on windows and linux and got the same result.
Thanks Jeff, for your informative email. The command work,
just like it does on Linux. YET... The results are NOT the same!
C:\Users\ddevienne>psql service=my17
ps
On Thu, Jun 5, 2025 at 1:40 PM Laurenz Albe wrote:
> On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote:
> > It clearly says "locale or builtin_locale", emphasis on the OR.
>
> You are right, and that's how it works on Linux.
> BUILTIN_LOCALE is not
On Tue, Jun 10, 2025 at 5:46 PM Dominique Devienne wrote:
> On Tue, Jun 10, 2025 at 4:27 PM Tom Lane wrote:
> > PQfinish is asynchronous: [...]
> > [...] pg_stat_activity() takes a snapshot of the view's contents
> Many thanks Tom. Didn't know either of those fa
Hi. We're getting unit-test failures that look like data-races,
which somehow are getting very frequent recently, tripping our CI.
Basically we have a `services` table, for service discovery, which
records the backend PID of its main DB Connection. Such that we can
account for "stale" / "zombie"
On Tue, Jun 10, 2025 at 4:27 PM Tom Lane wrote:
> Dominique Devienne writes:
> > So when and how fast does pg_stat_activity update, in the face of a
> > PQfinish?
>
> The shared state underlying pg_stat_activity is updated
> immediately when something changes. How
On Thu, Jul 10, 2025 at 6:25 PM Adrian Klaver wrote:
> On 7/10/25 04:48, Dominique Devienne wrote:
> > Seems so logical to me, that these hashing functions were available
> > are aggregates, I can't be the first one to think of that, can it?
>
> I've been on this l
On Thu, Jul 10, 2025 at 7:11 PM Ron Johnson wrote:
> On Thu, Jul 10, 2025 at 12:26 PM Adrian Klaver
> wrote:
>> On 7/10/25 04:48, Dominique Devienne wrote:
>> > Seems so logical to me, that these hashing functions were available
>> > are aggregates, I can'
We store scientific information in PostgreSQL, and some of that is
bytea and large, thus we must "chunk it" both for performance, and not
be limited to 1GB (we do exceed that, in rare occasions).
Recently I added md5/sha1 hashing support for such values (for various
reasons, to track corruptions i
On Thu, Jul 10, 2025 at 9:03 PM Merlin Moncure wrote:
> On Thu, Jul 10, 2025 at 5:48 AM Dominique Devienne
> wrote:
>> We store scientific information in PostgreSQL, and some of that is
>> bytea and large, thus we must "chunk it" both for performance, and not
>&g
On Fri, Jul 11, 2025 at 11:00 AM Dominique Devienne wrote:
> The current md5() and pgcrypto.digest() functions roll the x1
> init, xN process, and x1 finish into a single call, processing a
> single bytea (or perhaps more intelligently for TOAST'ed values, the
> 2K "rows&
On Fri, Jul 11, 2025 at 6:05 PM Florents Tselai
wrote:
> On Fri, Jul 11, 2025, 18:27 Adrian Klaver wrote:
>> [...] create an extension that incorporates the code.
>
> That's an ideal use case for an extension indeed .
Extensions are of no use to me, unfortunately, unless built-in and
official. S
301 - 343 of 343 matches
Mail list logo
