| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP checksums patch |
| Date: | 2012-11-09 15:18:05 |
| Message-ID: | CA+Tgmoa4Yb-XDQ5vDA470_Gy92rzxAt5Zhk=AjG73EMEV0jL5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 8, 2012 at 9:17 PM, Christopher Browne <cbbrowne(at)gmail(dot)com> wrote:
> I see one thing to be concerned about, there...
>
> I imagine it would not be a totally happy thing if the only way to switch it
> on/off was to use Slony or Londiste to replicate into a database with the
> opposite setting. (e.g. - This implies that built-in replication may only
> replicate into a database with the identical checksum configuration.)
Sure, I agree. I don't think it should stay that way forever, but
removing the burden of dealing with this issue from the initial commit
would likely allow that commit to happen this release cycle, perhaps
even in the next CommitFest. And then we'd have half a loaf, which is
better than none, and we could deal with the issues of switching it on
and off as a further enhancement.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-11-09 15:18:29 | Re: TRUNCATE SERIALIZABLE and frozen COPY |
| Previous Message | Simon Riggs | 2012-11-09 15:13:35 | Re: TRUNCATE SERIALIZABLE and frozen COPY |