Adminpack removal - Mailing list pgsql-hackers

From Philippe BEAUDOIN
Subject Adminpack removal
Date
Msg-id 19c2c5c3-aa11-4808-b4b4-cf61e4a3e4d6@free.fr
Whole thread Raw
Responses Re: Adminpack removal
Re: Adminpack removal
List pgsql-hackers
Hi,

I have just tested PG17 beta1 with the E-Maj solution I maintain. The 
only issue I found is the removal of the adminpack contrib.

In the emaj extension, which is the heart of the solution, and which is 
written in plpgsql, the code just uses the pg_file_unlink() function to 
automatically remove files produced by COPY TO statements when no rows 
have been written. In some specific use cases, it avoids the user to get 
a few interesting files among numerous empty files in a directory. I 
have found a workaround. That's a little bit ugly, but it works. So this 
is not blocking for me.

FYI, the project's repo is on github (https://github.com/dalibo/emaj), 
which was supposed to be scanned to detect potential adminpack usages.

Finally, I wouldn't be surprise if some other user projects or 
applications use adminpack as this is a simple way to get sql functions 
that write, rename or remove files.

Regards.




pgsql-hackers by date:

Previous
From: Shubham Khanna
Date:
Subject: Re: Pgoutput not capturing the generated columns
Next
From: Michael Paquier
Date:
Subject: Re: libpq: Fix lots of discrepancies in PQtrace