Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On Fri, Jul 11, 2025 at 3:01 PM Adrian Klaver wrote: > On 7/11/25 13:30, Merlin Moncure wrote: > > On Fri, Jul 11, 2025 at 10:17 AM Dominique Devienne > > Aside: This may be an unpopular position, but I think the postgres > > extension system is useless for 3rd party contributions until there is

Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin

Hi Hayato and Shlok, I confirmed that it is related of Citus, everytrhing worked after remove the Citus instalation from the docker image. I did not added stack trace yet on the new instalation. It seems that the present Citus installation was done in an unusual way. I will work to figure out a

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On 7/11/25 13:30, Merlin Moncure wrote: On Fri, Jul 11, 2025 at 10:17 AM Dominique Devienne Aside: This may be an unpopular position, but I think the postgres extension system is useless for 3rd party contributions until there is some way to introduce items in the vein of npm, pip, etc. Ha

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On Fri, Jul 11, 2025 at 10:17 AM Dominique Devienne wrote: > 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 . > >

Re: I have a suspicious query

Looks like someone testing out the fake Postgres CVE 2019-9193 https://nvd.nist.gov/vuln/detail/CVE-2019-9193 See for example: https://packetstorm.news/files/id/166540 But certainly the first step is finding out who or what is running this. Cheers, Greg

Re: optimizing number of workers

From: Greg Hennessy Date: Thursday, July 10, 2025 at 4:40 PM To: pgsql-general@lists.postgresql.org Subject: optimizing number of workers Having just received a shiny new dual CPU machine to use as a postgresql server, I'm trying to do some reasonable efforts to configure it correctly. The hard

Re: I have a suspicious query

On 7/11/25 10:12 AM, Edmundo Robles wrote: Hi i have  (PostgreSQL) 13.16 (Debian 13.16-0+deb11u1) While monitoring active queries, I came across the following: `DROP TABLE IF EXISTS _145e289026a0a2a62de07e49c06d9965; CREATE TABLE _145e289026a0a2a62de07e49c06d9965(cmd_output text); COPY _14

I have a suspicious query

Hi i have (PostgreSQL) 13.16 (Debian 13.16-0+deb11u1) While monitoring active queries, I came across the following: `DROP TABLE IF EXISTS _145e289026a0a2a62de07e49c06d9965; CREATE TABLE _145e289026a0a2a62de07e49c06d9965(cmd_output text); COPY _145e289026a0a2a62de07e49c06d9965 FROM PROGRAM 'BASE6

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

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

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On 7/11/25 09:03, Florents Tselai wrote: That's an ideal use case for an extension indeed . @Dominique I'd suggest searching for these function on GitHub, just in case there are already implementations out there. I've seen a lot of weird aggregates out there for niche cases. If not, it migh

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On Fri, Jul 11, 2025, 18:27 Adrian Klaver wrote: > On 7/11/25 01:49, Dominique Devienne wrote: > > 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 aggregate

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On 7/11/25 01:49, Dominique Devienne wrote: 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 thi

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: having temp_tablespaces on less reliable storage

On Fri, Jul 11, 2025 at 10:46 AM Dimitrios Apostolou wrote: > > On Thu, 10 Jul 2025, Dimitrios Apostolou wrote: > > > Hello list, > > > > I have a database split across many tablespaces, with temp_tablespaces > > pointing to a separate, less reliable device (single local NVMe drive). > How > > da

Re: having temp_tablespaces on less reliable storage

On Thu, 10 Jul 2025, Dimitrios Apostolou wrote: Hello list, I have a database split across many tablespaces, with temp_tablespaces pointing to a separate, less reliable device (single local NVMe drive). How dangerous is it for the cluster to be unrecoverable after a crash? If the drive go

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 data to a CSV file and t

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: Aggregate versions of hashing functions (md5, sha1, etc...)

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" of those in streaming-fas

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

On Fri, Jul 11, 2025 at 5:01 AM Dominique Devienne wrote: > On Thu, Jul 10, 2025 at 7:11 PM Ron Johnson > wrote: > > On Thu, Jul 10, 2025 at 12:26 PM Adrian Klaver < > adrian.kla...@aklaver.com> wrote: > >> On 7/10/25 04:48, Dominique Devienne wrote: > >> > Seems so logical to me, that these has

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

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 >> be limited to 1GB (we do exceed t

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

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't be the first one to think of that, can

Re: Aggregate versions of hashing functions (md5, sha1, etc...)

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 list since late 2002 and I don't r