On Thu, 27 Jun 2024, 07:34 Philippe BEAUDOIN, <phb.e...@free.fr> wrote: > > 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.
The extension at first glance doesn't currently seem to depend on adminpack: it is not included in the control file as dependency, and has not been included as a dependency since the creation of that file. Where else would you expect us to search for dependencies? Kind regards, Matthias van de Meent
