From: | Markus Wanner <markus(at)bluegap(dot)ch> |
---|---|
To: | koichi(dot)szk(at)gmail(dot)com |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, pgsql-cluster-hackers(at)postgresql(dot)org |
Subject: | Re: PgCon: who will be there? |
Date: | 2010-02-12 14:15:59 |
Message-ID: | d18f3ddd7fff5d8c2ceeaba0e426394f@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
Hi,
On Fri, 12 Feb 2010 22:21:23 +0900, Koichi Suzuki <koichi(dot)szk(at)gmail(dot)com>
wrote:
> 2010/2/12 Fujii Masao <masao(dot)fujii(at)gmail(dot)com>:
>> Umm.. do you think that the "Export snapshots to other sessions"
feature
>> is
>> completely independent of the snapshot management for the parallel
>> pg_dump?
>> If not, we should make the patch more extensible for the feature we
want?
I think a common, more general implementation is possible, but certainly
requires more work than a plain parallel pg_dump solution.
> I don't think so. But in the cluster, from my experience of PG-2, it
> is essential to manage snapshot consistent among all the node involved
> and we should be very careful to make other local tasks, for example,
> autovacuum and analyze, not disturb other transactions because they
> can become global long transactions very easily.
Well, I fear that's heavily dependent on the clustering solution. So I
think the first step will be to have a general purpose snapshot exporting /
cloning feature for a single node (i.e. usable for parallel querying).
Extending that to allow for distributed parallel querying is the next step.
Regards
Markus Wanner
From | Date | Subject | |
---|---|---|---|
Next Message | Koichi Suzuki | 2010-02-12 15:59:14 | Re: PgCon: who will be there? |
Previous Message | Koichi Suzuki | 2010-02-12 13:21:23 | Re: PgCon: who will be there? |