Re: Save The Date: Cluster-Hackers meeting May 21st

From: Selena Deckelmann <selena(at)chesnok(dot)com>
To: koichi(dot)szk(at)gmail(dot)com
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-cluster-hackers(at)postgresql(dot)org
Subject: Re: Save The Date: Cluster-Hackers meeting May 21st
Date: 2013-01-18 18:15:47
Message-ID: CAN1EF+zzSTrib_vrf8SE+cjirbQ7D+RTXH_FkKmUJm+xZe+RYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cluster-hackers pgsql-hackers

On Thu, Jan 17, 2013 at 5:24 PM, Koichi Suzuki <koichi(dot)szk(at)gmail(dot)com> wrote:

> Cluster summit should focus on what PG core should do to support
> various clustering use case and external tools. I think logical
> replication as well as DDL trigger should be given longer time to
> discuss.
>

+1

I won't be able to attend, unfortunately. But I hope that another
conversation happens at PgCon:

I am very interested in defining terms and setting up repeatable testing
for replication. I've started this wiki page:

http://wiki.postgresql.org/wiki/Binary_Replication_Tools

What I've found is that we don't use consistent terminology for these
tools, and they largely don't provide complete test cases that would help
someone setting up replication, backups and restores.

I've made some very rough shell scripts to test each one, but it needs
quite a bit more work. My ultimate goal is to see these kinds of scripts
incorporated into a Jenkins-like system that can automatically test new
releases against new versions of PostgreSQL. I find it really problematic
that we don't have a consistent way of doing this. Sysadmins who are
supporting these tools are particularly disadvantaged because they are
often supporting other databases and systems that have wildly different
backup procedures.

Just the other day, a friend told me about failing over and not having
secondary slaves follow the new master in a 9.0 system. The information
about which versions of Postgres support this feature is not easy to find.
I plan on incorporating that information in this wiki page over time -- but
again, we need to standardize terminology across all of the third-party
tools (open source and otherwise) so that people using these are not caught
by surprise when they are the most vulnerable to data loss.

-selena

--
http://chesnok.com

In response to

Browse pgsql-cluster-hackers by date

  From Date Subject
Next Message Manuel Hupp 2013-02-07 09:17:53 PostgreSQL Cluster with shared SAN Database
Previous Message Koichi Suzuki 2013-01-18 01:24:37 Re: Save The Date: Cluster-Hackers meeting May 21st

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-01-18 18:20:27 Re: missing rename support
Previous Message Andres Freund 2013-01-18 18:12:18 Re: in-catalog Extension Scripts and Control parameters (templates?)