Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal

From: Cynthia Shang <cynthia(dot)shang(at)crunchydata(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Vladimir Rusinov <vrusinov(at)google(dot)com>
Subject: Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal
Date: 2016-12-29 16:43:34
Message-ID: 20161229164334.32165.62475.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

1) I agree with Michael that we should make this change backward compatible. It would help PostgreSQL image if we did not break everyone's code. It costs businesses money to rewrite code (e.g. middle tier software, backup tools, etc), test and 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 was just unimportant logging data; I get that. I'm a little unclear why we need to change the functions - it would be less painful 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2016-12-29 17:04:54 Re: Improving RLS planning
Previous Message Peter Eisentraut 2016-12-29 15:57:27 Re: make more use of RoleSpec struct