Re: PG 14 pg_basebackup accepts --compress=server-zst option

2024-06-07 Thread Tom Lane
Ron Johnson writes: > On Fri, Jun 7, 2024 at 12:32 AM David G. Johnston < > david.g.johns...@gmail.com> wrote: >> I don’t see us adding an error message at this point. > Me neither. It just seemed odd. v14 thinks the argument of --compress must be an integer, and doesn't really bother with any

Re: Questions on logical replication

2024-06-07 Thread Adrian Klaver
On 6/6/24 15:19, Koen De Groote wrote: I'll give them a read, though it might take a few weekends Meanwhile, this seems to be what I'm looking for: From https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS

PG16.1 security breach?

2024-06-07 Thread David G. Johnston
On Friday, June 7, 2024, Laurenz Albe wrote: > On Fri, 2024-06-07 at 13:54 +, Zwettler Markus (OIZ) wrote: > > > Another point to keep in mind is that by default, execute privilege is > granted to > > > PUBLIC for newly created functions (see Section 5.7 for more > information). > > > > Argh.

Re: AW: [Extern] Re: PG16.1 security breach?

2024-06-07 Thread Adrian Klaver
On 6/7/24 06:54, Zwettler Markus (OIZ) wrote: -Ursprüngliche Nachricht- Von: Joe Conway Gesendet: Freitag, 7. Juni 2024 15:22 An: Zwettler Markus (OIZ) ; pgsql- gene...@lists.postgresql.org Betreff: [Extern] Re: PG16.1 security breach? On 6/7/24 07:04, Zwettler Markus (OIZ) wrote: A

Re: AW: [Extern] Re: PG16.1 security breach?

2024-06-07 Thread Laurenz Albe
On Fri, 2024-06-07 at 13:54 +, Zwettler Markus (OIZ) wrote: > > Another point to keep in mind is that by default, execute privilege is > > granted to > > PUBLIC for newly created functions (see Section 5.7 for more information). > > Argh. No! What a bad habit! > > Might be good idea for an e

Re: PG16.1 security breach?

2024-06-07 Thread David G. Johnston
On Friday, June 7, 2024, Zwettler Markus (OIZ) wrote: > > grant usage on schema oiz to public; > > > > The role is also able to execute the function even I revoke any execute > privilege explicitly: > > > > revoke execute on function oiz.f_set_dbowner (p_dbowner text, p_dbname > text) from testus

AW: [Extern] Re: PG16.1 security breach?

2024-06-07 Thread Zwettler Markus (OIZ)
> -Ursprüngliche Nachricht- > Von: Joe Conway > Gesendet: Freitag, 7. Juni 2024 15:22 > An: Zwettler Markus (OIZ) ; pgsql- > gene...@lists.postgresql.org > Betreff: [Extern] Re: PG16.1 security breach? > > On 6/7/24 07:04, Zwettler Markus (OIZ) wrote: > > I am running the following on Pos

Re: PG16.1 security breach?

2024-06-07 Thread Joe Conway
On 6/7/24 07:04, Zwettler Markus (OIZ) wrote: I am running the following on Postgres 16.1 in database "postgres" as a superuser: create or replace function oiz.f_set_dbowner (p_dbowner text, p_dbname text) create role testuser with password 'testuser' login; than this new role is ab

Re: Poor performance after restoring database from snapshot on AWS RDS

2024-06-07 Thread Ron Johnson
On Fri, Jun 7, 2024 at 4:36 AM Sam Kidman wrote: > > This is due to the way that RDS restores snapshots. > > Thanks, I never would have guessed. Would vacuum analyze be sufficient > to defeat the lazy loading or would we need to do something more > specific to our application? (for example. selec

Re: PG 14 pg_basebackup accepts --compress=server-zst option

2024-06-07 Thread Ron Johnson
On Fri, Jun 7, 2024 at 12:32 AM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Thursday, June 6, 2024, Kashif Zeeshan wrote: > >> Hi >> >> On Fri, Jun 7, 2024 at 6:54 AM Ron Johnson >> wrote: >> >>> >>> https://www.postgresql.org/docs/14/app-pgbasebackup.html doesn't >>> mention "--

PG16.1 security breach?

2024-06-07 Thread Zwettler Markus (OIZ)
I am running the following on Postgres 16.1 in database "postgres" as a superuser: revoke create on schema public from public; revoke create on database postgres from public; create schema if not exists oiz; revoke create on schema oiz from public; grant usage on schema oiz to public; create or

Re: Poor performance after restoring database from snapshot on AWS RDS

2024-06-07 Thread Sam Kidman
> This is due to the way that RDS restores snapshots. Thanks, I never would have guessed. Would vacuum analyze be sufficient to defeat the lazy loading or would we need to do something more specific to our application? (for example. select(*) on some commonly used tables) I think vacuum full woul

RE: Logical replication type- WAL recovery fails and changes the size of wal segment in archivedir

2024-06-07 Thread Meera Nair
Hi Laurenz, Thanks a lot! Regards, Meera -Original Message- From: Laurenz Albe Sent: Wednesday, June 5, 2024 3:56 PM To: Meera Nair ; pgsql-general@lists.postgresql.org Cc: Punit Pranesh Koujalgi ; B Ganesh Kishan Subject: Re: Logical replication type- WAL recovery fails and changes

RE: Logical replication type- WAL recovery fails and changes the size of wal segment in archivedir

2024-06-07 Thread Meera Nair
Hi Ron, We do have our own solution. We work for Commvault, a data protection company. We support backup of PostgreSQL in different ways - streaming, snapshot, block level, backup from standby server. PostgreSQL (commvault.com) Reg

Re: Oracle to Postgres - Transform Hash Partition

2024-06-07 Thread Laurenz Albe
On Thu, 2024-06-06 at 11:28 -0500, David Barbour wrote: > Been an Oracle DBA for quite a while and we're moving from Oracle to Postgres. > > I have a table that I need to transform into a hash partitioned table. > I've gone through all the steps to create a hash partitioned table, with 8 > partit