Brad Nicholson wrote:
> Excellent addition. I suggest in 24.1 - Shared Disk Failover something
> about the risk of having two postmasters come up on the same data
> directory, which is entirely possible if the old master doesn't release
> the disk in time.
I have added a mention of this.
---
Excellent addition. I suggest in 24.1 - Shared Disk Failover something
about the risk of having two postmasters come up on the same data
directory, which is entirely possible if the old master doesn't release
the disk in time.
On Tue, 2006-11-14 at 15:11 -0500, Bruce Momjian wrote:
> I wrote th
I wrote this for the 8.2 documentation. Let me know if it helps or you
have other suggestions:
http://developer.postgresql.org/pgdocs/postgres/failover.html
---
Moiz Kothari wrote:
> Guys,
>
> I have been thinking
Shoaib,Also just so you know, we plan to use SLES 10 OS. so also let me know the compatibility of EnterpriseDB to the OS.Regards,MoizOn 10/31/06,
Shoaib Mir <[EMAIL PROTECTED]> wrote:
Moiz,H, I think pg_controldata output might help you there to get these stats. pg_controldata can be found in
Moiz,Yes, EnterpriseDB is compatible with SLES 10.Thank you,-Shoaib MirEnterpriseDB (www.enterprisedb.com)
On 11/1/06, Moiz Kothari <[EMAIL PROTECTED]> wrote:
Shoaib,Also just so you know, we plan to use SLES 10 OS. so also let me know the compatibility of EnterpriseDB to the OS.Regards,Moi
Shoaib,I see you are with enterprise DB, does enterpriseDB support clustering? if it does then probably i can think in terms of it to be an option to go for.I need to come to a decision soon on it as we have to decide on what Database to go for.
Thanks for all your help.Regards,Moiz Kothari
On 10/
Moiz,H, I think pg_controldata output might help you there to get these stats. pg_controldata can be found in the PostgreSQL /bin folder.Thank you,-Shoaib MirEnterpriseDB (
www.enterprisedb.com)On 10/31/06, Moiz Kothari <[EMAIL PROTECTED]> wrote:
Shoaib,This sounds really like what i ne
Shoaib,This sounds really like what i need, but again 8.2 is in beta. Just one question, i dunno if i am thinking in right direction, but is there anyway of finding out the END XID, transaction id and OID of last archived WAL log applied to the database. I was thinking if i can get that value then
Hi Moiz,This might help you :) --> http://developer.postgresql.org/pgdocs/postgres/warm-standby.htmlThanks,---Shoaib Mir
EnterpriseDB (www.enterprisedb.com)On 10/30/06, Andrew Sullivan <
[EMAIL PROTECTED]> wrote:On Mon, Oct 30, 2006 at 06:41:54PM +0530, Moiz Kothari wrote:
> I agree that PGClus
On Mon, Oct 30, 2006 at 06:41:54PM +0530, Moiz Kothari wrote:
> I agree that PGCluster might be a better option, i dont want to go with
> Slony because of primary key constraints.
I don't know what the "primary key constraints" issue you have is,
but Slony would be inappropriate for a "100% failo
Moiz,Have you tried PGPool? as that comes with a built-in load balancer as well.For PITR in HA scenario, I dont remember where I read but some one did it like this:- Make base backup for the primary server say five time a day (depends on the transactions happening on the db server)
- Automate these
Shoaib,I agree that PGCluster might be a better option, i dont want to go with Slony because of primary key constraints. But PGCluster is a good option, the only concerns are :1) It might slow down the process a bit. as confirmation happens after transaction gets comitted to all the nodes.
2) Its d
Hi Moiz,If I had to choose for your case where you want to direct your selects to slave node and inserts/updates on master, I would have opted for Slony or PGCluster. Using PITR for HA can be a good option if you want to switch between primary and secondary server, where you can store the archive f
Moiz,
basically a special JDBC driver connects to a controller that populates
the data across your DB nodes (and allows load balancing and failover),
see http://sequoia.continuent.org/ for more!
Regards, Oliver.
---(end of broadcast)---
TIP 1: if p
Hi Oliver,I din't quite understand that.. Do you mean have application populate data across to all the DB machines?Can you elaborate on that please...Regards,Moiz Kothari
On 10/30/06, Mensinger, Oliver <[EMAIL PROTECTED]> wrote:
Moiz,it depends on your application (must use JDBC), but you may want
Shoaib,It sure does, i saw PGCLUSTER, but 3 reasons for having a postgres specific solution.1) If pgcluster stops further development, it would be lot more hassel when upgrading to a different version of postgres.
2) Postgres specific solution would help alot going ahead in future. 3) Also architec
Moiz,
it depends on your application (must use JDBC), but you may want to look
at Sequoia, the continuation of the C-JDBC project.
Regards, Oliver.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
There is this project which actually is not released yet, but something that you want to achieve :)http://pgfoundry.org/projects/pgpitrhaRegards,---
Shoaib MirEnterpriseDB (www.enterprisedb.com)On 10/30/06, Ben Suffolk <
[EMAIL PROTECTED]> wrote:> Guys,>> I have been thinking about this and wan
Guys,
I have been thinking about this and wanted to see if it can be
achived. I wanted to make a 100% failover solution for my postgres
databases. The first thing that comes to my mind is doing it using
WAL logs. Am attaching the diagram for which i will write more here.
While its not the
Guys,I have been thinking about this and wanted to see if it can be achived. I wanted to make a 100% failover solution for my postgres databases. The first thing that comes to my mind is doing it using WAL logs. Am attaching the diagram for which i will write more here.
I was thinking if i can have
20 matches
Mail list logo
