forked from CrunchyData/pgbouncer_fdw
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
27 lines (17 loc) · 2.39 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
v1.0.0
-- IMPORTANT NOTE: All objects in this extension are dropped and recreated as part of this update. Privileges ARE NOT preserved as part of this update, so please ensure privileges you have on these objects are preserved before upgrading so that they can be reapplied. Note that execution by PUBLIC on the admin functions is once again revoked by this update.
-- Add support for gathering statistics from multiple pgBouncer targets
-- A new configuration table has been added to define the names of all FDW servers.
-- All views have an additional column to identify the pgBouncer target
-- All administrative command functions have had a parameter for the FDW server name added to them. These functions intentionally do not use the configuration table to avoid accidentally running an admin command on multiple servers.
-- Add better support for multiple versions of PgBouncer. Support for 1.17 has been backported into this version of pgbouncer_fdw.
v0.5
-- Update to support pgBouncer 1.18.0. Note that as of v0.5, this extension requires at least version 1.18.0 of pgBouncer. If you still need to support an older version, v0.4 works with pgBouncer 1.16 and v0.3 works with older versions of pgBouncer. There are no other changes in this version other than a compatibility update.
-- Several views are dropped and recreated as part of this update. Privileges should be preserved, but it is recommended to double-check them.
v0.4
-- Updated to support pgBouncer 1.16.0. Note that as of v0.4, this extension requires at least version 1.16.0 of pgBouncer. If you still need to support an older version, v0.3 still works and there are no other changes in this version other than a compatibility update.
-- All views are dropped and recreated as part of this update. Privileges should be preserved, but it is recommended to double-check them.
v0.3
-- Add command functions to allow running pgBouncer commands on the target server. Note that the role defined in the user mapping must be given admin access to the pgBouncer admin console. It is recommended to have separate roles in the PostgreSQL database to allow there to be separate user mappings: one for simple monitoring and another for admin console access.
v0.2
-- Add "pgbouncer_" prefix to all object names to help avoid naming collisions with commonly named objects. Now no longer generally necessary to install in dedicated schema, but still recommended if possible.