Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

> "NFS" is a key word that does not inspire confidence in PostgreSQL circles... Coming back to this, I just implemented 9P, which should translates to proper semantics for FSYNC. mount -t 9p -o trans=tcp,port=5564,version=9p2000.L,msize=65536,access=user 127.0.0.1 /mnt/9p Best, P

Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture

On Wed, 23 Jul 2025 12:13:26 +0100 Achilleas Mantzios wrote: … > Have you consider pgpool-ii ?  I know most support / service companies > push for patroni, and manually separating read / write traffic from > within the app, Indeed > but I still find pgpool's query routing very nice. Using Pgp

Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture

On 6/18/25 18:12, vijay patil wrote: Hi Team, I am planning to implement a PostgreSQL High Availability (HA) and Load Balancing setup and would greatly appreciate your feedback on the architecture we've designed (see attached diagram). image.png *Overview of the Setup:* *

Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture

> > Is this architecture considered a best practice within the PostgreSQL > community? I would say Patroni is probably "best practice", but there are other people out there happy with, and expert with, repmgr as well. Are there any potential bottlenecks or failure points I

Re: Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU

> Our setup: 5 Node Patroni Cluster with PostgreSQL 16.9. > db1: current leader > db2: sync-replica > db3/4/5: replica >   > The replicas connect to the leader using the host IP of the leader. So there > are > 4 walsender for patroni, 1 sync and 3 async. >   > The p

Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU

(Note: I have also attached the whole email for better readability of the logs) Hello! Our setup: 5 Node Patroni Cluster with PostgreSQL 16.9. db1: current leader db2: sync-replica db3/4/5: replica The replicas connect to the leader using the host IP of the leader. So there are 4 walsender for

Re: Regarding logical replication issues with PostgreSQL versions 16 and above

On Fri, 2025-07-18 at 19:08 +0800, yexiu-glory wrote: > I'm facing a problem here: our business requires logical data replication to > other > departments, but at the same time, sensitive fields need to be filtered out. > Therefore, we used the column filtering function when creating logical > re

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

u clarify how exactly you're running >>> postgres in your tests? A specific AWS service? What's the test >>> infrastructure that sits above the file system? >>> >>> On Thu, Jul 17, 2025 at 11:59 PM Pierre Barre wrote: >>>> Hi everyone, >>

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

u clarify how exactly you're running > postgres in your tests? A specific AWS service? What's the test > infrastructure that sits above the file system? > > On Thu, Jul 17, 2025 at 11:59 PM Pierre Barre wrote: > > Hi everyone, > > I wanted to share a project I&#x

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

Now, I'm trying to understand how CAP theorem applies here. Traditional PostgreSQL replication has clear CAP trade-offs - you choose between consistency and availability during partitions. But when PostgreSQL instances share storage rather than replicate: - Consistency seems maintained

Regarding logical replication issues with PostgreSQL versions 16 and above

I'm facing a problem here: our business requires logical data replication to other departments, but at the same time, sensitive fields need to be filtered out. Therefore, we used the column filtering function when creating logical replication. If we use `alter table table1 replica identity defau

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

fy how exactly you're running > postgres in your tests? A specific AWS service? What's the test > infrastructure that sits above the file system? > > On Thu, Jul 17, 2025 at 11:59 PM Pierre Barre wrote: >> Hi everyone, >> >> I wanted to share a project I

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

ote: > Hi everyone, > > I wanted to share a project I've been working on that enables PostgreSQL > to run on S3 storage while maintaining performance comparable to local > NVMe. The approach uses block-level access rather than trying to map > filesystem operations to S3 object

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

hole system gradually by starting with throwable workloads (e.g., persistent volumes in CI), then moving to data we can afford to lose, then backups, and finally to production data. >> P.S. The full project includes a custom NFS filesystem too. > > "NFS" is a key word th

Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance

it is not everything. If things perform surprisingly well, people become suspicious. > P.S. The full project includes a custom NFS filesystem too. "NFS" is a key word that does not inspire confidence in PostgreSQL circles... Yours, Laurenz Albe

PostgreSQL on S3-backed Block Storage with Near-Local Performance

Hi everyone, I wanted to share a project I've been working on that enables PostgreSQL to run on S3 storage while maintaining performance comparable to local NVMe. The approach uses block-level access rather than trying to map filesystem operations to S3 objects. ZeroFS: https://githu

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On Wed, Jul 16, 2025 at 8:42 PM Greg Sabino Mullane wrote: > On Wed, Jul 16, 2025 at 9:25 AM Amol Inamdar wrote: > >> >>1. NFS mount point is for /nfs-mount/postgres (and permissions locked >>down so that Postgres cannot create directories in here) >>2. Postgres data directory is /nf

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Amol Inamdar writes: > @Laurenz Albe >> If you pre-create the data directory with the appropriate permissions, >> what keeps you from giving ownership to the correct user too? > Our NFS server is not a regular linux based server, > it's on zOS (Mainframes) with AT-TLS security enabled, > hence i

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

ol will ensure only the Posgres user can > read/write to > > this directory) > > Considering the above scenario/setup, what is the danger of removing the > ownership check > > in miscinit.c checkDataDir() function ? > > The danger is that somebody else than the Postgr

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On Wed, Jul 16, 2025 at 9:25 AM Amol Inamdar wrote: > >1. NFS mount point is for /nfs-mount/postgres (and permissions locked >down so that Postgres cannot create directories in here) >2. Postgres data directory is /nfs-mount/postgres/db >3. > >With secured NFS + AT-TLS setup P

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

cinit.c checkDataDir() function ?  The danger is that somebody else than the PostgreSQL user has permissions on the data directory. You will argue that that somebody is root, and root has these permissions anyway. But there is another reason why PostgreSQL insists that the PostgreSQL user owns th

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Quoting Tom's earlier email: "(But I too *would not use Postgres-over-NFS for any critical data*. Too many moving parts. It's tough enough to ensure crash safety with local storage.)" You're going through a lot of security effort to implement a Worst Practice. On Wed, Jul 16, 2025 at 9:25 AM Amo

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Hi All, I would like to rephrase the question a little bit, below is how our setup going to be 1. NFS mount point is for /nfs-mount/postgres (and permissions locked down so that Postgres cannot create directories in here) 2. Postgres data directory is /nfs-mount/postgres/db 3. Wit

Re:Question Regarding COPY Command Handling of Line Breaks in PostgreSQL

ot;gzh" wrote: Dear, I am encountering an issue with the COPY command in PostgreSQL regarding the handling of line breaks in data fields. My PostgreSQL instance is installed on a Linux system. When I use the COPY command to export data to a CSV file and then import the same CSV file back into

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Thanks Tom and Laurenz for the explanation. Let me try out a few things and get back to you if needed. Thanks, Amol On Mon, Jul 14, 2025 at 7:37 PM Tom Lane wrote: > Laurenz Albe writes: > > It is not a good idea to have a mount point be the data directory. > > ^^^ This. ^^^ > > That is primar

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Thanks Laurenz. On Mon, Jul 14, 2025 at 8:11 PM Laurenz Albe wrote: > On Mon, 2025-07-14 at 18:32 +0530, Amol Inamdar wrote: > > > The data directory can either be created by "initdb", in which case > > > the mount point must allow the PostgreSQL user to create a

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

em, there is a lost+found directory where fsck places links to orphaned inodes. If the PostgreSQL user owns the mount point and wants to use "initdb" to create a data directory in it, the program will fail and complain that the directory is not empty. The danger is great that the use

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Benjamin Wang writes: > I am not sure whether PostgreSQL depends on system call `fsyncdata` to > sync data to disk. If yes, then I don't think it's safe to use NFS. Well, that's a whole other discussion. The point about mount directories applies to any sort of dismountable

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On Mon, Jul 14, 2025 at 12:02 PM Benjamin Wang wrote: > I am not sure whether PostgreSQL depends on system call `fsyncdata` to > sync data to disk. > https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-SYNC-METHOD David J.

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

I am not sure whether PostgreSQL depends on system call `fsyncdata` to sync data to disk. If yes, then I don't think it's safe to use NFS. When `fsyncdata` returns success, it doesn't mean the data has really been synced to disk. But if PostgreSQL crashes right after it returns suc

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

"Peter J. Holzer" writes: > On 2025-07-14 10:07:20 -0400, Tom Lane wrote: >> That is primarily for safety reasons: if for some reason the >> filesystem gets dismounted, or hasn't come on-line yet during >> a reboot, you do not want Postgres to be able to write on the >> underlying mount-point dire

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On 2025-07-14 10:07:20 -0400, Tom Lane wrote: > Laurenz Albe writes: > > It is not a good idea to have a mount point be the data directory. > > ^^^ This. ^^^ > > That is primarily for safety reasons: if for some reason the > filesystem gets dismounted, or hasn't come on-line yet during > a reboo

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On Mon, 2025-07-14 at 18:32 +0530, Amol Inamdar wrote: > > The data directory can either be created by "initdb", in which case > > the mount point must allow the PostgreSQL user to create a directory. > > You could set the group of the mount point to the group of the

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Laurenz Albe writes: > It is not a good idea to have a mount point be the data directory. ^^^ This. ^^^ That is primarily for safety reasons: if for some reason the filesystem gets dismounted, or hasn't come on-line yet during a reboot, you do not want Postgres to be able to write on the underly

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Thanks Laurenz, The data directory can either be created by "initdb", in which case the mount point must allow the PostgreSQL user to create a directory. You could set the group of the mount point to the group of the PostgreSQL user and use permissions 1770, which should be perfectly s

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

> I'm currently running PostgreSQL version 16.6 inside a Docker container > > (base image: UBI 9), using Docker Compose. The PostgreSQL data directory > > is mounted from an NFS volume hosted on a z/OS NFS server. > > > > The environment has a few constraints: > > >

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

her be created by "initdb", in which case the mount point must allow the PostgreSQL user to create a directory. You could set the group of the mount point to the group of the PostgreSQL user and use permissions 1770, which should be perfectly safe. Alternatively, the root user could cr

Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

On Mon, 2025-07-14 at 11:19 +0530, Amol Inamdar wrote: > I'm currently running PostgreSQL version 16.6 inside a Docker container > (base image: UBI 9), using Docker Compose. The PostgreSQL data directory > is mounted from an NFS volume hosted on a z/OS NFS server. > > The e

Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)

Dear PostgreSQL Community, I'm currently running PostgreSQL version 16.6 inside a Docker container (base image: UBI 9), using Docker Compose. The PostgreSQL data directory is mounted from an NFS volume hosted on a z/OS NFS server. The environment has a few constraints: - The NFS server ru

Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL

On 7/11/25 06:07, Ron Johnson wrote: On Fri, Jul 11, 2025 at 8:20 AM gzh > wrote: What PG version? What's the full command (including both shell and SQL commands)? Also provide a sample of the original exported data and a sample of the data after it is imported. --

Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL

On Fri, Jul 11, 2025 at 8:20 AM gzh wrote: > Dear, > > I am encountering an issue with the COPY command in PostgreSQL regarding > the handling of line breaks in data fields. My PostgreSQL instance is > installed on a Linux system. > > When I use the COPY command to export d

Question Regarding COPY Command Handling of Line Breaks in PostgreSQL

Dear, I am encountering an issue with the COPY command in PostgreSQL regarding the handling of line breaks in data fields. My PostgreSQL instance is installed on a Linux system. When I use the COPY command to export data to a CSV file and then import the same CSV file back into the database

Re: Postgresql support for Windows Server 2025

On Wed, 2025-07-02 at 20:12 +0530, Gaurav Aradhya wrote: > Can you please let me know when Postgresql 17.x  shall be supported for > Windows Server 2025? Greatly appreciated your feedback. If you want to know if it is working, the best answer is "as soon as someone donates a W

Re: Postgresql support for Windows Server 2025

On 7/2/25 07:42, Gaurav Aradhya wrote: Greetings, Can you please let me know when Postgresql 17.x  shall be supported for Windows Server 2025? Greatly appreciated your feedback. The Windows packaging is done by EDB, someone from there will need to see this and respond or you could contact

Re: Postgresql support for Windows Server 2025

On Wednesday, July 2, 2025, Gaurav Aradhya wrote: > > Can you please let me know when Postgresql 17.x shall be supported for > Windows Server 2025? Greatly appreciated your feedback. > Impossible to guess when someone may choose to set up a build farm member running that OS. David J.

Postgresql support for Windows Server 2025

Greetings, Can you please let me know when Postgresql 17.x shall be supported for Windows Server 2025? Greatly appreciated your feedback. Thanks Gaurav

Re: Simulate a PITR in postgresql 16

simulate a PITR in postgresql 16 with the following steps: > > directorys: > /data/primary > /data/base > /data/wals > /data/csv > > 1- Create cluster to primary postgresql: > /usr/pgsql-16/bin/initd -D /data/primary > > 2- Start Cluster ( port) > /usr/pgsql-16/b

Re: Simulate a PITR in postgresql 16

Am 30.06.2025 um 21:45 schrieb Ron Johnson: Using PgBackRest might be more convenient, since it handles everything you need, is multithreaded, never removes too many wal files, compresses files if you want and also encrypts them if you want. I agree, with pgBackRest it's basically: pgbackre

Re: Simulate a PITR in postgresql 16

## Franklin Anderson de Oliveira Souza (frankli...@gmail.com): > LOG: database system was shut down at 2025-06-30 12:15:28 -04 > cp: cannot stat '/dados/temp/wals/0002.history': No such file or directory > - > > > The restore_command requires the .history file but it does not

Re: Simulate a PITR in postgresql 16

On 6/30/25 12:35, Franklin Anderson de Oliveira Souza wrote: I'm trying to simulate a PITR in postgresql 16 with the following steps: - LOG: starting PostgreSQL 16.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22), 64-bit LOG: listening on

Re: Simulate a PITR in postgresql 16

x27;s just more convenient.) On Mon, Jun 30, 2025 at 3:35 PM Franklin Anderson de Oliveira Souza < frankli...@gmail.com> wrote: > I'm trying to simulate a PITR in postgresql 16 with the following steps: > > directorys: > /data/primary > /data/base > /data/wals > /data

Simulate a PITR in postgresql 16

I'm trying to simulate a PITR in postgresql 16 with the following steps: directorys: /data/primary /data/base /data/wals /data/csv 1- Create cluster to primary postgresql: /usr/pgsql-16/bin/initd -D /data/primary 2- Start Cluster ( port) /usr/pgsql-16/bin/pg_ctl -D /data/primary sta

Re: PostgreSQL 17.5 - could not map dynamic shared memory segment

Hi, Thanks for the good point: $ sysctl vm.overcommit_memory vm.overcommit_memory = 0 That is a difference, the old pg11 running on Ubuntu 18.4 had disabled overcommit (vm.overcommit_memory = 2). Anyway, on a dedicated DB server box with 123GB RAM running only vacuum (14 parallel processes (2GB

Re: PostgreSQL 17.5 - could not map dynamic shared memory segment

On 6/21/25 23:09, Aleš Zelený wrote: > Hello, > ... > > The application benefits from parallel queries, so despite the first > temptation to disable parallel queries (based on log entries correlation > only, but is that the root cause?) I did not want to disable parallel > queries, if there is anot

PostgreSQL 17.5 - could not map dynamic shared memory segment

Hello, After upgrading from (old good no longer supported Pg11) to PostgreSQL 17.5 via pg_dump & pg_restore vacuum started reporting errors: ERROR: could not map dynamic shared memory segment Vacuumdb was invoked: /usr/lib/postgresql/17/bin/vacuumdb -p 5433 -Fvaz -j 12 -v The vacuum fini

Request for Feedback on PostgreSQL HA + Load Balancing Architecture

Hi Team, I am planning to implement a PostgreSQL High Availability (HA) and Load Balancing setup and would greatly appreciate your feedback on the architecture we've designed (see attached diagram). [image: image.png] *Overview of the Setup:* - Two PostgreSQL nodes (VM1 an

Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION

Hello, Belatedly, I came back to this issue in the release notes. Here's a query for correctly reporting the problem and not reporting the cases where there isn't a problem: SELECT conrelid::pg_catalog.regclass AS "constrained table", conname AS constraint, confrelid::pg_catalog.re

Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION

Alvaro Herrera writes: > I'm going to fix the query in the release notes for all past branches > now, to avoid confusing people upgrading in the future ... hopefully not > many, but I don't think it's going to be zero people. OK, thanks. regards, tom lane

Re: Postgresql 18beta1 and SPI changes

PostgreSQL 17, I only got minor compilation problems that I managed to resolve fairly easily. However this didn't prove to be the case with PostgreSQL 18beta1, it proved harder to compile and as my fears were verified, it has serious problems. My question : is 18's SPI stabilized ? Can I start w

Re: Postgresql 18beta1 and SPI changes

Dear All, Dear Tom On 5/11/25 16:20, Tom Lane wrote: Achilleas Mantzios writes: We use are own version of DBmirror, we run our replication in a highly fine grained manner. So every upgrade I have to make the code compile and test. Up to PostgreSQL 17, I only got minor compilation problems

Re: Updating to PostgreSQL 17.5

Hi Tom, > On 11 May 2025, at 21:36, Tom Lane wrote: > > Sorry --- it means BRIN indexes that use one of the "xxx_bloom_ops" opclasses. > > https://www.postgresql.org/docs/current/brin.html#BRIN-BUILTIN-OPCLASSES Ah, so that'd reduce my monster query to: select concat ('reindex index "', s

Re: Updating to PostgreSQL 17.5

Paul Foerster writes: > the release notes for PostgreSQL 17.5 > (https://www.postgresql.org/docs/17/release-17-5.html) state: > "Also, if you have any BRIN bloom indexes, it may be advisable to reindex > them after updating." > I don't know what exactly that m

Updating to PostgreSQL 17.5

Hi, the release notes for PostgreSQL 17.5 (https://www.postgresql.org/docs/17/release-17-5.html) state: "Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating." I don't know what exactly that means. So I read about BRIN and BLOOM indexes

Re: Postgresql 18beta1 and SPI changes

Achilleas Mantzios writes: > We use are own version of DBmirror, we run our replication in a highly > fine grained manner. So every upgrade I have to make the code compile > and test. Up to PostgreSQL 17, I only got minor compilation problems > that I managed to resolve fairly eas

Postgresql 18beta1 and SPI changes

Dear members We use are own version of DBmirror, we run our replication in a highly fine grained manner. So every upgrade I have to make the code compile and test. Up to PostgreSQL 17, I only got minor compilation problems that I managed to resolve fairly easily. However this didn't pro

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669‏

https://www.postgresql.org/download/macosx/, personally I'd > give Postgres.app a. try or the installation via Homebrew (A bit less easy > than the GUI app) > > Philipp > > On Thu, May 8, 2025, at 8:17 PM, איתי זרחוביץ wrote: > > ,Hello > I have a MacBook with an M4 ch

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669‏

There's multiple ways recommended on > https://www.postgresql.org/download/macosx/, personally I'd > give Postgres.app a. try or the installation via Homebrew (A bit less easy > than the GUI app) > > Philipp > > On Thu, May 8, 2025, at 8:17 PM, איתי זרחוביץ wrote: &

Re: Looking for pgbench Benchmark Results Across PostgreSQL Versions

sults Across PostgreSQL Versions Hi everyone, I’ve been searching for a website that provides pgbench results for different PostgreSQL versions, from 11 to 18, including the latest beta or alpha releases. Does anyone know of such a site? Thanks!

Re: Looking for pgbench Benchmark Results Across PostgreSQL Versions

> On 8 May 2025, at 22:07, Özkan Pakdil wrote: > > Hi everyone, > I’ve been searching for a website that provides pgbench results for different > PostgreSQL versions, from 11 to 18, including the latest beta or alpha > releases. > Does anyone know of such a site? There

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669‏

u doing to see this error message? >>>> >>>> There's multiple ways recommended on >>>> https://www.postgresql.org/download/macosx/, personally I'd give >>>> Postgres.app a. try or the installation via Homebrew (A bit less easy than >&

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669‏

oing to see this error message? >> >> There's multiple ways recommended on >> https://www.postgresql.org/download/macosx/, personally I'd give >> Postgres.app a. try or the installation via Homebrew (A bit less easy than >> the GUI app) >> &

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669‏

Homebrew (A bit less easy than the GUI app) Philipp On Thu, May 8, 2025, at 8:17 PM, איתי זרחוביץ wrote: > ,Hello > I have a MacBook with an M4 chip. I tried installing PostgreSQL version 17.5, > but after the > installation, I received the following error > _LSOpenURLsWithComplet

Looking for pgbench Benchmark Results Across PostgreSQL Versions

Hi everyone, I’ve been searching for a website that provides pgbench results for different PostgreSQL versions, from 11 to 18, including the latest beta or alpha releases. Does anyone know of such a site? Thanks!

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669

On 5/8/25 12:41, איתי זרחוביץ wrote: You need to remember to hit Reply All so the list is included in the conversation. Ccing list I tried before a hour to download Try now and see what happens. Also try the postgres.app link I posted previously. -- Adrian Klaver adrian.kla...@aklaver

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669

On 5/8/25 12:02, איתי זרחוביץ wrote: Reply to list also: Ccing list. I tried to download from this link: https://www.enterprisedb.com/downloads/postgres-postgresql-downloads <https://www.enterprisedb.com/downloads/postgres-postgresql-downloads> and than i got the

Re: Issue Launching PostgreSQL on MacBook M4 – Error -10669

On 5/8/25 05:17, איתי זרחוביץ wrote: ,Hello I have a MacBook with an M4 chip. I tried installing PostgreSQL version 17.5, but after the installation, I received the following error | _LSOpenURLsWithCompletionHandler() failed with error -10669 (1) .and the application fails to launch A

Re: EDB Download for PostgreSQL 17.5 is broken

Hi Ertan Correct Version 17.5.0 is being downloaded and it may be a cache issue. Regards Kashif Zeeshan EDB On Thu, May 8, 2025 at 9:29 PM Ertan Küçükoglu wrote: > Hello, > > I am just writing here with the hope that there are some EDB contacts here. > > The 17.5 version Windows x86-64 downloa

Re: EDB Download for PostgreSQL 17.5 is broken

563> and this is actually getting you a 17.4-2 download. When I click on the link I above I get 17.5-1. When I click through from here: https://www.enterprisedb.com/downloads/postgres-postgresql-downloads I get 17.4-2. Looks like some sort of caching issue. Thanks & Regards, Ertan

EDB Download for PostgreSQL 17.5 is broken

Hello, I am just writing here with the hope that there are some EDB contacts here. The 17.5 version Windows x86-64 download link on EDB is https://sbp.enterprisedb.com/getfile.jsp?fileid=1259563 and this is actually getting you a 17.4-2 download. Thanks & Regards, Ertan

Re: SQL ERROR subquery uses ungrouped column in PostgreSQL

On Thu, 1 May 2025 at 00:29, PALAYRET Jacques wrote: > => In the subquery, the semantic analysis of the query considers the column " > dat " instead of the expression " to_char(dat,'mm') ", which is actually > a grouped column. > Is this normal? How can I simply resolve the problem? Calcula

SQL ERROR subquery uses ungrouped column in PostgreSQL

Hello, I have an unexpected error in my following query (of course, the query has been simplified here to request help): SELECT num_poste, to_char(dat, 'MM')::integer dat, CASE FLOOR((TO_NUMBER(TO_CHAR(dat,'DD'),'99')-1)/10) WHEN 0 THEN 1 WHEN 1 THEN 2 ELSE 3 END::smallint AS num_decade

Bash automation for PostgreSQL

misconfigured with my PostgreSQL syntax. If you find a bug in LinuxHA, please submit a bug report to bugs.launchpad.net/linuxha/+filebug. Kind regards, Travis Bean

RE: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

Dear Tom, Laurenz, and Dominique, Thank you all very much for your helpful and detailed explanations. Your insights clarified the behavior change in PostgreSQL 15 perfectly, and I now have a clear understanding of the issue I was encountering. I really appreciate your time and support. Best

Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

Laurenz Albe writes: > On Thu, 2025-04-17 at 05:17 +, 王　博 wrote: >> 1. In PostgreSQL 15 and later: >>    The following SQL causes a syntax error unless a space is added after the >> `?`: >> SELECT * FROM table WHERE a = ?AND b = 123; >>    → Adding a s

Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

On Thu, 2025-04-17 at 05:17 +, 王　博 wrote: > We have encountered unexpected SQL parsing errors during application upgrades > from > PostgreSQL 14 to 15 and 16, related to the use of JDBC-style parameter > placeholders (`?`) in our legacy applications. >   > Specifically: >

Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

On Thu, Apr 17, 2025 at 11:13 AM 王　博 wrote: > Hello PostgreSQL Community, > We have encountered unexpected SQL parsing errors during application upgrades > from PostgreSQL 14 to 15 and 16, related to the use of JDBC-style parameter > placeholders (`?`) in our legacy applicat

Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

Hello PostgreSQL Community, We have encountered unexpected SQL parsing errors during application upgrades from PostgreSQL 14 to 15 and 16, related to the use of JDBC-style parameter placeholders (`?`) in our legacy applications. Specifically: 1. In PostgreSQL 15 and later: The following

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

On Wed, Apr 16, 2025 at 03:53:53PM -0400, Ron Johnson wrote: > On Wed, Apr 16, 2025 at 3:42 PM Nico Williams wrote: > > I would care about what happened. To know what happened I'd have to see > > either only audit logs for committed transactions, or also see the > > COMMIT and ROLLBACK statements

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

On Wed, Apr 16, 2025 at 3:42 PM Nico Williams wrote: > On Wed, Apr 16, 2025 at 02:43:59PM -0400, Ron Johnson wrote: > > You'll have to bring that up with the PgAudit maintainer. Note, though, > > that the purpose of PgAudit is not "recreate the database from audit > logs"; > > it's "what Auditor

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

On Wed, Apr 16, 2025 at 02:43:59PM -0400, Ron Johnson wrote: > You'll have to bring that up with the PgAudit maintainer. Note, though, > that the purpose of PgAudit is not "recreate the database from audit logs"; > it's "what Auditors care about". In my experience, auditors do not care > about CO

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

>>> >>> One issue we have with pgaudit is that it prints AUDIT records even if >>> the xaction gets rollbacked, how do you alleviate that ? >>> >>> >>> yours, >>> >>> Kenan Çiftçi >>> >>> On Tue, Apr 15, 2025 at 1:

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

e that ? yours, Kenan Çiftçi On Tue, Apr 15, 2025 at 1:44 PM vijay patil wrote: Hi All, We are exploring auditing solutions for our PostgreSQL database and are considering using |pgaudit| for this purpose. However,

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

gt;> yours, >> >> Kenan Çiftçi >> >> On Tue, Apr 15, 2025 at 1:44 PM vijay patil >> wrote: >> >>> Hi All, >>> >>> We are exploring auditing solutions for our PostgreSQL database and are >>> considering using p

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

gets rollbacked, how do you alleviate that ? yours, Kenan Çiftçi On Tue, Apr 15, 2025 at 1:44 PM vijay patil wrote: Hi All, We are exploring auditing solutions for our PostgreSQL database and are considering using |pgaudit| for this purpose. Howeve

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

t; > yours, > > Kenan Çiftçi > > On Tue, Apr 15, 2025 at 1:44 PM vijay patil > wrote: > >> Hi All, >> >> We are exploring auditing solutions for our PostgreSQL database and are >> considering using pgaudit for this purpose. However, we have a few

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

do you alleviate that ? yours, Kenan Çiftçi On Tue, Apr 15, 2025 at 1:44 PM vijay patil wrote: Hi All, We are exploring auditing solutions for our PostgreSQL database and are considering using |pgaudit| for this purpose. However, we have a few questions: 1

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

> yours, > > Kenan Çiftçi > > On Tue, Apr 15, 2025 at 1:44 PM vijay patil > wrote: > >> Hi All, >> >> We are exploring auditing solutions for our PostgreSQL database and are >> considering using pgaudit for this purpose. However, we have a few >>

Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

Hi All, We are exploring auditing solutions for our PostgreSQL database and are considering using pgaudit for this purpose. However, we have a few questions: 1. *What is the best tool for auditing PostgreSQL databases?* - We are specifically looking for a solution that offers

Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

Hi, You can use pgaudit and pgauditlogtofile extension ( https://github.com/fmbiete/pgauditlogtofile) together to write audit logs in a separate file. yours, Kenan Çiftçi On Tue, Apr 15, 2025 at 1:44 PM vijay patil wrote: > Hi All, > > We are exploring auditing solutions for our P

Re: To take backup of Postgresql Database without large objects

On 4/11/25 23:05, David G. Johnston wrote: On Friday, April 11, 2025, Adrian Klaver > wrote: On 4/11/25 22:06, sivapostg...@yahoo.com wrote: Either my command should be wrong or I'm missing something. This w

  1   2   3   4   5   6   7   8   9   10   >