Version 0.64 of package Pg has just been released in NonGNU ELPA. You can now find it in M-x list-packages RET.
Pg describes itself as: ================================================= Socket-level interface to the PostgreSQL database ================================================= More at https://elpa.nongnu.org/nongnu/pg.html ## Summary: # pg.el -- Emacs Lisp socket-level interface to the PostgreSQL RDBMS ## Recent NEWS: # Changelog ## [0.64] - 2026-03-28 - Save all connection info in the pgcon object, for possible later use by `pg-cancel`, rather than only a subset of the user-specified connection info. The function `pgcon-connect-info` which returned this subset is deprecated in 2026-03, replaced by `pgcon-connect-plist` which returns a full list including previously unsaved aspects such as the `tls-info`. - New function `pg-clone-connection` that establishes a new connection to PostgreSQL “cloned” from its argument, an existing PostgreSQL connection. Opens a new connection to the same PostgreSQL instance, using the same authentication information. This function works both for TCP connections to the database and for local (Unix socket) connections. - Add code to detect PostgreSQL variants SereneDB, Apache Cloudberry and Picodata. - Add workarounds for the SereneDB variant, which does not currently implement the standard information schema but implements PostgreSQL-style system tables. - Add workarounds for the Picodata variant, which does not implement many of the PostgreSQL system tables. ## [0.63] - 2026-02-08 - Add support for looking up connection passwords using the Emacs auth-source functionality. If variable `pg-use-auth-source` is non-nil and a null value for password is provided to `pg-connect-plist` or `pg-connect-local` (including indirectly via `pg-connect/uri` or `pg-connect/uri`), the password will be looked up in configured auth-sources. If not found, an empty string is used as password. ## [0.62] - 2025-12-26 - New function `pg-table-acl` which returns the access control list for a specified table. - Type aliases are recognized as type names in `pg-exec-prepared`, in additional to the type names present in the `pg_type` system table. This means that you can use `bigint` as an alternative to `int8`, `real` as an alternative to `float4`, `bit varying` as an alternative to `bit`, for example. The aliases are also the canonical type names as shown by function `pg_typeof`. - Rename functions `pg-read-attributes`, `pg-read-tuple`, `pg-read-char`, `pg-unread-char`, `pg-read-net-int`, `pg-read-int`, `pg-read-chars`, `pg-read-string`, `pg-send-char`, `pg-send-string`, `pg-send-octets`, `pg-send-uint`, `pg-send-net-uint` to use the naming convention for internal functions (`pg--` prefix). - Microsoft Windows: add additional sleep using `sleep-for` when waiting for network data. The existing calls to `accept-process-output` with a timeout are insufficient on this platform when reading large resultsets. Further testing is needed to determine whether this is also necessary on other non-Linux platforms like MS-DOS and Darwin. - Improve parsing of arrays that contain NULL elements: they will correctly be parsed as the `pg-null-marker` for arrays of bits, arrays of booleans, arrays of strings. ## [0.61] - 2025-11-22 - Add support for providing a password for authentication as a function, rather than as a string. This allows for integration with the auth-source functionality in Emacs, and helps to reduce the length of time where passwords remain present in RAM. Patch from @Kaylebor. - New error class `pg-invalid-sql-statement-name` which is signalled when an invalid name is given to a prepared query. - New error class `pg-invalid-cursor-name` which is signalled when an invalid name is used for a cursor. - Integer arrays and floating point arrays containing NULL values will now be parsed correctly. ## [0.60] - 2025-09-21 - Add support for version 3.2 of the wire protocol, introduced in PostgreSQL v18. The only change with respect to the previously supported version 3.0 is the length of the key used to authenticate requests to cancel an ongoing query. As for libpq, we default to using version 3.0, because several PostgreSQL variants do not support version 3.2 and have not yet implemented the protocol version downgrade functionality that is designed into the protocol. ... ...
