Re: tcp keepalives not sent during long query

2022-12-14 Thread Willy-Bas Loos
The version is PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit

Re: tcp keepalives not sent during long query

2022-12-14 Thread Willy-Bas Loos
On Wed, Dec 14, 2022 at 6:38 PM Tom Lane wrote: > It'd be worth doing > > show tcp_keepalives_idle; > > Wow, you're right! It's in the postgresql.conf but it isn't set when I reload the server A restart also doesn't do it and even doing SET tcp_keepalives_idle=120; doesn't work. It gives me a con

Re: Test if a database has any privilege granted to public

2022-12-14 Thread Tom Lane
Ron writes: > Off-topic, but you don't need all those text casts. Indeed. Something like this ought to do it: =# select datname from pg_database where 0::oid = any(select (aclexplode(datacl)).grantee); datname template1 template0 regression (3 rows)

Re: Test if a database has any privilege granted to public

2022-12-14 Thread Ron
Off-topic, but you don't need all those text casts. On 12/14/22 23:44, Bryn Llewellyn wrote: I want to adopt a rule that no database in my cluster has any privilege granted to public. It suits me best to encapsulate the test as a boolean function thus: *function mgr.db_has_priv_granted_to_pub

Test if a database has any privilege granted to public

2022-12-14 Thread Bryn Llewellyn
I want to adopt a rule that no database in my cluster has any privilege granted to public. It suits me best to encapsulate the test as a boolean function thus: function mgr.db_has_priv_granted_to_public(db in name) where "mgr" is a convenient schema for various admin utilities. I have implement

Re: compiling postgres on windows - how to deal with unmatched file extension?

2022-12-14 Thread Mladen Gogala
On 12/13/22 23:55, Yang, T. Andy wrote: src/backend/bootstrap/bootparse.c': No such file or directory 'src/backend/parser/gram.c': No such file or directory Have you tried using cygwin? -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com

Re: Dumping security labels for extension owned tables?

2022-12-14 Thread Michel Pelletier
On Wed, Dec 14, 2022 at 11:29 AM Julien Rouhaud wrote: > > Note that if a table is part of an extension, pg_extension_config_dump > will only lead pg_dump to emit the table data, not the table DDL. The > table itself must be entirely created by the extension script, and any > modification done a

Re: Dumping security labels for extension owned tables?

2022-12-14 Thread Julien Rouhaud
Hi On Wed, Dec 14, 2022 at 7:02 PM Michel Pelletier wrote: > > I have an issue I've run into that is puzzling me, I have an extension > pgsodium that uses SECURITY LABEL to trigger the creation of encrypting > triggers and a decrypting view. When a table not associated with an > extension is

Dumping security labels for extension owned tables?

2022-12-14 Thread Michel Pelletier
Hello, I have an issue I've run into that is puzzling me, I have an extension pgsodium that uses SECURITY LABEL to trigger the creation of encrypting triggers and a decrypting view. When a table not associated with an extension is dumped, the label gets dumped as well, and that's fine. But if I

Re: tcp keepalives not sent during long query

2022-12-14 Thread Tom Lane
Willy-Bas Loos writes: > Thanks for your answer. I was afraid someone would say that... > I was hoping that the keepalives would be more of a matter of cooperation > between postgres and the OS. No, we just apply the setting to the open socket and trust the OS to do it. Are you quite certain tha

Re: tcp keepalives not sent during long query

2022-12-14 Thread Willy-Bas Loos
Thanks for your answer. I was afraid someone would say that... I was hoping that the keepalives would be more of a matter of cooperation between postgres and the OS. On Wed, Dec 14, 2022 at 10:52 AM Laurenz Albe wrote: > On Wed, 2022-12-14 at 08:55 +0100, Willy-Bas Loos wrote: > > Some users of

Re: tcp keepalives not sent during long query

2022-12-14 Thread Laurenz Albe
On Wed, 2022-12-14 at 08:55 +0100, Willy-Bas Loos wrote: > Some users of our database have a NAT firewall and keep a postgres client > (e.g. pgAdmin ) > open for hours. To prevent the connection from being killed by the firewall > due to inactivity, > we configured tcp_keepalives_idle = 120 so th