Re: [GENERAL] Tutorials on high availability Postgresql setup?

[Digimer]

On 10-10-07 02:27 AM, Andy wrote:
> Is there any tutorials or detailed instructions on how to set up HA 
> postgresql & failover? The documentation 
> (http://www.postgresql.org/docs/9.0/interactive/warm-standby-failover.html) 
> on this topics is pretty scarce.
> 
> The scenario I'm most interested in is this:
> 
> 2 servers - a master and a hot standby. All writes are sent to master, reads 
> are split between master and hot standby.
> 
> 1) If the hot standby goes down, how do I redirect reads to the master?
> 2) If the master fails
> -how do I automatically promote the standby to master and send all 
> reads/writes to the new master?
> -what happens when the old master comes back up? Do I need to so anything 
> to make it catches up to the new master?
> 
> Thanks.

One option would be to create a simple 2-node cluster and run your PgSQL
server in a migrateable VM backed by a SAN or, if your budget is more
modest, a simple DRBD device.

Personally, I like to use RHCS (Red Hat Cluster Services) with a DRBD
array becking clustered LVM with Xen VMs (domU) on dedicated LVs. This
doesn't dictate the OS version hosting postgres though, so if you've got
a particular set of requirement, you can meet them.

Then in the case of planned outage, you can hot-migrate your VM to the
other node. In the case of catastrophic failure, the surviving node can
boot the PgSQL server and it would come back as if it had simply lost
power. In either case, you don't need to worry about IPs, special
configs or what have you.

-- 
Digimer
E-Mail: li...@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Problem using CASTed timestamp column

[Digimer]

Hi all,

  I've got an odd problem. I've got a column with a non-standard
date/time in it that I carve up and re-cast as a timestamp. This works
fine. Now though, I am trying to check/restrict my results to dates
before now() and it's telling me that the columns doesn't exist.

http://pastebin.com/sExiBynp

  Any hints on what I am doing wrong?

Thanks!

-- 
Digimer
E-Mail: digi...@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Duda sobre campo null!!!

[Digimer]

On 10-08-16 09:51 PM, Lazaro Ruben Garcia Martinez wrote:
> Hola a todos, desde hace mucho tiempo tengo una una duda relacionada con
> los campos nullos, quería saber si tanto el empleo como la presencia de
> los mismos ya sea en tablas pequeñas o grandes, pude afectar de alguna
> forma el rendimiento del sistema, ademas quisiera saber que
> inconvenientes puede presentar.
> 
> Saludos y muchisimas gracias por su tiempo.

Lo siento, pero esto es una lista de correo Inglés. Usted recibirá más
ayuda si usted puede volver a preguntar en Inglés.

Creo que NULL no tiene resultados reales afectados. Es sólo otro estado;
True, False, Null.


Google translated, sorry for the poor Spanish.

-- 
Digimer
E-Mail: li...@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general