Re: LOCALE C.UTF-8 on EDB Windows v17 server

On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote: > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8' > locale_provider 'builtin' template template0 I believe what you want is: create database "dd_v168" encoding 'UTF8' builtin_locale 'C.UTF-8' locale_provider 'builtin' tem

Re: Yet more ROLE changes in v18 beta1???

Dominique Devienne writes: > Unfortunately, digging into this is not something I can do right away. > v18 is still a few months out, I do hope I can investigate before that. It'd be good if you could prioritize that a bit more. If there is a bug rather than an intentional change here, we'd much

Re: LOCALE C.UTF-8 on EDB Windows v17 server

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' > locale_provider 'builtin' template template0 > > On Windows, I'm getting > > 2025-06-04 14:07:41.227419 B 155 ErrorRespon

Re: Yet more ROLE changes in v18 beta1???

On Wed, 2025-06-04 at 18:42 +0200, Dominique Devienne wrote: > 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 con

Re: Yet more ROLE changes in v18 beta1???

On 6/4/25 16:17, Ron Johnson wrote: On Wed, Jun 4, 2025 at 1:53 PM Adrian Klaver > wrote: Shouldn't the client version only matter for the SQL generated by psql meta-commands?  (Because what meta-commands drop roles?) I would think if the version did not m

Re: Sudden increase in n_dead_tup with no corresponding insert/update/delete

Note also that 15.6 is about 18 months old. Upgrading really does only take a few minutes, if you download the binaries before installation. On Wed, Jun 4, 2025 at 2:37 PM Matthew Tice wrote: > > > On Jun 3, 2025, at 6:23 PM, David Rowley wrote: > > > > On Wed, 4 Jun 2025 at 07:22, Matthew Tic

Re: Yet more ROLE changes in v18 beta1???

On Wed, Jun 4, 2025 at 1:53 PM Adrian Klaver wrote: > > > On 6/4/25 9:39 AM, Dominique Devienne wrote: > > 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,

Re: Feature request: Settings to disable comments and multiple statements in a connection

Glen K writes: > My feature requests are thus: > Provide a client connection option (and/or implement the backend support) to > disallow comments in SQL statements I don't believe that this would move the needle on SQL-injection safety by enough to be worth doing. An injection attack is normal

Feature request: Settings to disable comments and multiple statements in a connection

Given that most SQL injections involve use of comments and/or insertion of semi-colons to start a new statement, it seems to me that injection attacks could be substantially reduced if client connections could be configured t

Re: Sudden increase in n_dead_tup with no corresponding insert/update/delete

> On Jun 3, 2025, at 6:23 PM, David Rowley wrote: > > On Wed, 4 Jun 2025 at 07:22, Matthew Tice wrote: >> Tue 03 Jun 2025 07:13:11 PM UTC (every 1s) >> n_dead_tup | 5038 >> autoanalyze_count | 3078 > >> Tue 03 Jun 2025 07:13:12 PM UTC (every 1s) >> n_dead_tup | 1290579 >>

Re: Yet more ROLE changes in v18 beta1???

On 6/4/25 9:39 AM, Dominique Devienne wrote: 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

Re: Yet more ROLE changes in v18 beta1???

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.postgresql.org/gitweb/?p=postgresql.git&a=commitd

Re: Yet more ROLE changes in v18 beta1???

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

Re: Yet more ROLE changes in v18 beta1???

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.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=01463e1cc Ensure that AFTER triggers run as the instigati

Re: Yet more ROLE changes in v18 beta1???

On 6/4/25 06:52, Dominique Devienne wrote: Thanks, --DD PS: I'm not ruling out our code is at fault. Especially since we have conditional code based on the server version these days. But I'm pre-emptively asking for known changes in this area, to the experts. $ ./myruntests.csh tests_pdgm_sche

Re: Yet more ROLE changes in v18 beta1???

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

Re: Yet more ROLE changes in v18 beta1???

Hi Dominique, 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 changes either, but that could very easily be a case of me not paying enou

Yet more ROLE changes in v18 beta1???

(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

Re: pg_constraint catalog changes in v18 beta1???

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.postgresql.org/doc

pg_constraint catalog changes in v18 beta1???

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

LOCALE C.UTF-8 on EDB Windows v17 server

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