Search Postgresql Archives

pgpool2 vs sequoia

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

i would like to use a statement replication for postgresql

i have found the following solutions:
- pgpool 
- pgpool2
- sequoia (jdbc, formerly known as c-jdbc)

pgpool has only two nodes, so this is not an option.

I will never change my underlying database, of course :-) 
So i dont have any advantage of the sequoia jdbc abstraction. i'd rather 
sometimes use other tools than jdbc to access the database with some perl 
scripts, so this is an advantage for pgpool2. but sequoia looks very nice at 
first glance.

What are other advantages/disadvantages in respect of
- performance/scalability
- stability
- support / ease-of-use / etc.

i would be very happy if someone can share his/her expierence with such a 
solution. 

kind regards,
janning


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux