Ok, slony supports two kinds of operation here: failover (which moves the
master node to a new one without the old master node being present, it also
drops the old node from replication) and move set (which moves the master node
with cooperation)
The usecases for these two are slightly differen
am Fri, dem 08.06.2007, um 1:22:14 -0700 mailte choksi folgendes:
> Hi all,
>
> I had a database which uses to hold some 50 Mill records and disk
> space used was 103 GB. I deleted around 34 Mill records but still the
> disk size is same. Can some on please shed some light on this.
DELETE only
What about "Daffodil Replicator" - GPL -
http://sourceforge.net/projects/daffodilreplica/
--
Thanks,
Eugene Ogurtsov
Internal Development Chief Architect
SWsoft, Inc.
Craig A. James wrote:
Looking for replication solutions, I find:
Slony-I
Seems good, single master only, master is a sing
Craig James wrote:
Andreas Kostyrka wrote:
Slony provides near instantaneous failovers (in the single digit seconds
range). You can script an automatic failover if the master server
becomes unreachable.
But Slony slaves are read-only, correct? So the system isn't fully
functional once the m
Andreas Kostyrka wrote:
Slony provides near instantaneous failovers (in the single digit seconds
range). You can script an automatic failover if the master server
becomes unreachable.
But Slony slaves are read-only, correct? So the system isn't fully functional
once the master goes down.
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Most of our data is replicated offline using custom tools tailored to
> our loading pattern, but we have a small amount of "global" information,
> such as user signups, system configuration, advertisements, and such,
> that go into a single small (~5
Hi all,
I had a database which uses to hold some 50 Mill records and disk
space used was 103 GB. I deleted around 34 Mill records but still the
disk size is same. Can some on please shed some light on this.
Thank in advance for all the help.
Dhawal Choksi
---(end of bro
Hi all,
It seems that I have an issue with the performance of a PostgreSQL server.
I'm running write-intensive, TPC-C like tests. The workload consist of
150 to 200 thousand transactions. The performance varies dramatically,
between 5 and more than 9 hours (I don't have the exact figure for th
Hi Andrew
On 11-Jun-07, at 11:34 AM, Andrew Sullivan wrote:
On Mon, Jun 11, 2007 at 11:09:42AM -0400, Dave Cramer wrote:
and set them to anything remotely close to 128GB.
Well, we'd give 25% of it to postgres, and the rest to the OS.
Are you quite sure that PostgreSQL's management of the bu
Craig James wrote:
> Tyrrill, Ed wrote:
> > QUERY PLAN
> >
> >
>
> >
>
> > ---
> > Merge Left Join (cost=38725295.93..42505394.70 rows=
Looking for replication solutions, I find:
Slony-I
Seems good, single master only, master is a single point of failure,
no good failover system for electing a new master or having a failed
master rejoin the cluster. Slave databases are mostly for safety or
for parallelizing queries for perfo
Thanks to all who replied and filled in the blanks. The problem with the web
is you never know if you've missed something.
Joshua D. Drake wrote:
Looking for replication solutions, I find...
Slony-II
Dead
Wow, I'm surprised. Is it dead for lack of need, lack of resources, too
complex, or
>>> On Thu, Jun 14, 2007 at 6:14 PM, in message <[EMAIL PROTECTED]>,
Craig James <[EMAIL PROTECTED]> wrote:
> Looking for replication solutions, I find:
>
> Slony-I
> Slony-II
> PGReplication
> PGCluster
You wouldn't guess it from the name, but pgpool actually supports replication:
http://pg
On 6/15/07, Craig James <[EMAIL PROTECTED]> wrote:
[snip]
Is this a good summary of the status of replication? Have I missed any
important solutions or mischaracterized anything?
* Mammoth Replicator, commercial.
* Continuent uni/cluster, commercial
(http://www.continuent.com/index.php?optio
Which replication problem are you trying to solve?
On Thu, 14 Jun 2007, Craig James wrote:
Looking for replication solutions, I find:
Slony-I
Seems good, single master only, master is a single point of failure,
no good failover system for electing a new master or having a failed
master rejoin
Craig James wrote:
Looking for replication solutions, I find:
Slony-I
Seems good, single master only, master is a single point of failure,
no good failover system for electing a new master or having a failed
master rejoin the cluster. Slave databases are mostly for safety or
for parallelizing q
Looking for replication solutions, I find:
Slony-I
Seems good, single master only, master is a single point of failure,
no good failover system for electing a new master or having a failed
master rejoin the cluster. Slave databases are mostly for safety or
for parallelizing queries for performan
On 6/14/07, Guillaume Smet <[EMAIL PROTECTED]> wrote:
On 6/14/07, Y Sidhu <[EMAIL PROTECTED]> wrote:
> Can anyone share what value they have set log_min_duration_statement to?
It's OT but we use different values for different databases and needs.
On a very loaded database with a lot of complex
On 6/14/07, Y Sidhu <[EMAIL PROTECTED]> wrote:
Can anyone share what value they have set log_min_duration_statement to?
It's OT but we use different values for different databases and needs.
On a very loaded database with a lot of complex queries (lots of join
on big tables, proximity queries,
On 6/14/07, Dimitri Fontaine <[EMAIL PROTECTED]> wrote:
Le jeudi 14 juin 2007, Sabin Coanda a écrit:
> I'd like to understand completely the report generated by VACUUM
VERBOSE.
> Please tell me where is it documented ?
Try the pgfouine reporting tool :
http://pgfouine.projects.postgresql.org/
Hi Guillaume,
Very interesting !
Merci beaucoup,
Sabin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Wed, 2007-06-13 at 18:33 +0200, RESTOUX, Loïc wrote:
> 2) I believed that the poor performances during the vacuum freeze were due to
> the obsolete data statistics. But after a full restart of the dabatase,
> performances are good. Does PostgreSQL rebuild his statistics during startup
> ?
Le jeudi 14 juin 2007, Sabin Coanda a écrit :
> I'd like to understand completely the report generated by VACUUM VERBOSE.
> Please tell me where is it documented ?
Try the pgfouine reporting tool :
http://pgfouine.projects.postgresql.org/
http://pgfouine.projects.postgresql.org/reports/sample_
Sabin,
On 6/14/07, Sabin Coanda <[EMAIL PROTECTED]> wrote:
I'd like to understand completely the report generated by VACUUM VERBOSE.
Please tell me where is it documented ?
You can take a look to what I did for pgFouine:
http://pgfouine.projects.postgresql.org/vacuum.html
--
Guillaume
--
On Jun 13, 2007, at 10:36 PM, Francisco Reyes wrote:
FreeBSD, indeed. The vendor, Partners Data Systems, did a wonderful
This one?
http://www.partnersdata.com
that's the one.
job ensuring that everything integrated well to the point of
talking with various FreeBSD developers, LSI engi
Hi there,
I'd like to understand completely the report generated by VACUUM VERBOSE.
Please tell me where is it documented ?
TIA,
Sabin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
26 matches
Mail list logo
