how to create cluster(loadbanacing) of postgresql server

http://slony.info/

On 30/01/2008, yogesh m chaudhari <yogesh@banasdairy.coop> wrote:

Hi Friends
Can any Guys help me to create postgresql Cluster.
Is there any useful link or Info. related to cluster than pl mail me.

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/&gt;, and is
believed to be clean.

--
Brian Modra Land line: +27 23 5411 462
Mobile: +27 79 183 8059
6 Jan Louw Str, Prince Albert, 6930
Postal: P.O. Box 2, Prince Albert 6930
South Africa

Hi,

yogesh m chaudhari wrote:

Can any Guys help me to create postgresql Cluster.
Is there any useful link or Info. related to cluster than pl mail me.

There are various possibilities, for a good start, check the official docu:
http://www.postgresql.org/docs/8.2/static/high-availability.html

As well as the advocacy wiki:

http://developer.postgresql.org/index.php/Replication%2C_Clustering%2C_and_Connection_Pooling

If you are interested in what I'm doing:
http://www.postgres-r.org

BTW: please don't cross post

Regards

Markus

Hi Everybody,

I am searching for a pg_xxxxx view that would allow me to view the
properties of an index.
- the fillfactor it was created with
- the amount of free space on a page(s) storing the index ( assuming
that it was created with a fillfactor and the index has incurred updates
since the creation taking up some space reserved by the fillfactor
during the load).

The usage of a fillfactor nor fragmentation info does not get displayed
in pgAdminIII. In SQL Server 2005 the analogous views would be:
Obcc showcontig and sys.dm_index_physical_stats

Perhaps there is another way to determine fragmentation of indexes in
Postgres, any hint would be much appreciated.

Sincerely,
Kasia

Kasia Tuszynska wrote:

I am searching for a pg_xxxxx view that would allow me to view the
properties of an index.
- the fillfactor it was created with

Catalog pg_class, column reloptions.

- the amount of free space on a page(s) storing the index ( assuming
that it was created with a fillfactor and the index has incurred updates
since the creation taking up some space reserved by the fillfactor
during the load).

The usage of a fillfactor nor fragmentation info does not get displayed
in pgAdminIII.

Fillfactor information is available with pgAdmin III 1.8.

In SQL Server 2005 the analogous views would be:

Obcc showcontig and sys.dm_index_physical_stats

Perhaps there is another way to determine fragmentation of indexes in
Postgres, any hint would be much appreciated.

Try pgstattuple module contrib. See
http://www.postgresql.org/docs/8.3/static/pgstattuple.html for more
informations.

Regards.

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com