Horton

Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal

Jim Nasby <jim.nasby@bluetreble.com>

View thread View on postgr.es
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Stephen Frost <sfrost@snowman.net>, Michael Paquier <michael.paquier@gmail.com>
Cc: Vladimir Rusinov <vrusinov@google.com>, Cynthia Shang <cynthia.shang@crunchydata.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-01-02T17:30:40Z
Lists: pgsql-hackers 
On 1/1/17 9:48 AM, Peter Eisentraut wrote:
> On 12/30/16 9:57 AM, Stephen Frost wrote:
>> Additionally, people who are actually using these bits of the system are
>> almost certainly going to have to adjust things for the directory
>> change,
>
> Some *xlog* functions are commonly used to measure replay lag.  That
> usage would not be affected by the directory renaming.  Renaming those
> functions would only serve to annoy users and have them delay their
> upgrades.

Perhaps we should split the difference and do what we did for XML: 
provide a contrib module with alias functions using the old (xlog) names.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

Commits

  1. Remove all references to "xlog" from SQL-callable functions in pg_proc.

  2. Replace pg_shadow and pg_group by new role-capable catalogs pg_authid