Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal - Mailing list pgsql-hackers

From Cynthia Shang
Subject Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
Date
Msg-id 20161229164334.32165.62475.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tree view 
1) I agree with Michael that we should make this change backward compatible. It would help PostgreSQL image if we did
notbreak everyone's code. It costs businesses money to rewrite code (e.g. middle tier software, backup tools, etc),
testand redeploy to their customers. 
 

2) We decided to rename the pg_xlog directory because people were deleting it when disks were getting full thinking it
wasjust unimportant logging data; I get that. I'm a little unclear why we need to change the functions - it would be
lesspainful to our users and less risky if we just left them as is. Could someone please elaborate why this change is
necessary?I'm just trying to understand that.
 

Thanks,
-Cynthia

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] make more use of RoleSpec struct
Next
From: Dean Rasheed
Date:
Subject: Re: [HACKERS] Improving RLS planning