pgbench help

On 12/24/2012 08:50 AM, Atri Sharma wrote:

I have two 9.2 servers running in different data directories and
installation directories. One of them(the main one) has its bin in the
path of my system.The other one does not, hence, I need to use the
complete path(/usr/local/pgsql/...).

I want to run pgbench on the second server. How should I configure
pgbench to use the second server's psql?

Hi,

I'm by no means an expert in pgbench, but this is client software
relying on libpq.
You can make it work against the secondary server simply by specifying
its port with -p option or PGPORT environment variable.

If that matters, to make sure that the right version of libpq is being
used, you can use LD_LIBRARY_PATH, something like

export LD_LIBRARY_PATH = /usr/local/pgsql/lib

ann use if possible the pgbench from the secondary install.

Make sure both servers aren't running at the same time :-)

Regards,

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

On Mon, Dec 24, 2012 at 4:13 PM, Georges Racinet <gracinet@anybox.fr> wrote:

On 12/24/2012 08:50 AM, Atri Sharma wrote:

I have two 9.2 servers running in different data directories and
installation directories. One of them(the main one) has its bin in the
path of my system.The other one does not, hence, I need to use the
complete path(/usr/local/pgsql/...).

I want to run pgbench on the second server. How should I configure
pgbench to use the second server's psql?

Hi,

I'm by no means an expert in pgbench, but this is client software
relying on libpq.
You can make it work against the secondary server simply by specifying
its port with -p option or PGPORT environment variable.

If that matters, to make sure that the right version of libpq is being
used, you can use LD_LIBRARY_PATH, something like

export LD_LIBRARY_PATH = /usr/local/pgsql/lib

ann use if possible the pgbench from the secondary install.

Make sure both servers aren't running at the same time :-)

Thanks a ton, I get it now.

Atri

--
Regards,

Atri
l'apprenant

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

On 12/24/2012 2:43 AM, Georges Racinet wrote:

Make sure both servers aren't running at the same time

why? its perfectly OK to ahve severla postgres servers running at once,
as long as they are on different port numbers. I generally use 5432,
5433, 5434, etc for this. mostly for development, or for migration,
not so much on a production system where performance is important.

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

On 12/24/2012 12:32 PM, John R Pierce wrote:

On 12/24/2012 2:43 AM, Georges Racinet wrote:

Make sure both servers aren't running at the same time

why? its perfectly OK to ahve severla postgres servers running at
once, as long as they are on different port numbers. I generally use
5432, 5433, 5434, etc for this. mostly for development, or for
migration, not so much on a production system where performance is
important.

You're perfectly right. I'm used to have several clusters on the same
host (application testing in my case).
In this benchmark context, though, I just was being wary that they may
interfere, For instance, I suppose that an autovacuum wakeup in one
should lower performance results of the other.

Sorry it that sounded more general than that.

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

Sent from my iPad

On 24-Dec-2012, at 17:15, Georges Racinet <gracinet@anybox.fr> wrote:

On 12/24/2012 12:32 PM, John R Pierce wrote:

On 12/24/2012 2:43 AM, Georges Racinet wrote:

Make sure both servers aren't running at the same time

why? its perfectly OK to ahve severla postgres servers running at
once, as long as they are on different port numbers. I generally use
5432, 5433, 5434, etc for this. mostly for development, or for
migration, not so much on a production system where performance is
important.

You're perfectly right. I'm used to have several clusters on the same
host (application testing in my case).
In this benchmark context, though, I just was being wary that they may
interfere, For instance, I suppose that an autovacuum wakeup in one
should lower performance results of the other.

Sorry it that sounded more general than that.

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

Hi,

Thanks for the extensive discussion.

In my case,vacuum performance plays an important role. Hence, I shall run only one server at a time while profiling.

Thanks a ton,

Atri

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