On Friday 13 December 2002 00:52, Aravind Vinnakota wrote:
> Hi all,
> I am looking for a postgreSQL client (okay with command line client) for
> installing on a Solaris 8 machine. The basic idea is to use the client and
> retreive the data from a database running on another machine. So, I want
>
On Thursday 12 December 2002 01:35 am, Jesus Sandoval wrote:
> 3) In my design of data logging, I only have one "logging table" for all
> the application, but this logging table has to have the table name and the
> column name of what is being changed, inserted or deteled, like the
> following:
>
Hi!
I need help, i mounted a Postgresql server on IBM
netserver with RAID 5 134 GB, 2.5 GB de RAM and two Xeon 1.4 ghz.
I installed postgresql 7.3 in this box, my database
have over 25 millons of records, and everything is slow.
i optimized with indexes,vacuum analyze and tuning
up the kernel
I was asking on the pyPgSQL list whether the PQrequestCancel() would allow
that if a user submitting queries from Python closed the Python shell, the
query would be cancelled (a la ^C in psql). This led me to:
If the connection from which a synchronous query
("libpq->connection.query()") was subm
On Fri, 13 Dec 2002, Ing. Gabriel Monsalvo wrote:
> Hi!
> I need help, i mounted a Postgresql server on IBM netserver with RAID 5 134 GB, 2.5
>GB de RAM and two Xeon 1.4 ghz.
> I installed postgresql 7.3 in this box, my database have over 25 millons of records,
>and everything is slow.
> i opti
This is what I get when I do a pg_dumpall. I have *no* idea what to do
here. I'm trying to migrate from 7.0.3 to 7.2.1, and the manual said to
use pg_dumpall for this rather than using pg_dump on each database
(which works). *Please* help.
[postgres@everest /tmp]$ pg_dumpall -u > file
Password:
Justin Georgeson <[EMAIL PROTECTED]> writes:
> This is what I get when I do a pg_dumpall. I have *no* idea what to do
> here.
It's a lot easier to do pg_dumpall if you are not using password
authentication. Consider downgrading your pg_hba setting to "trust" for
local connections while you do th
Tom Lane wrote:
Justin Georgeson <[EMAIL PROTECTED]> writes:
This is what I get when I do a pg_dumpall. I have *no* idea what to do
here.
It's a lot easier to do pg_dumpall if you are not using password
authentication. Consider downgrading your pg_hba setting to "trust" for
local connectio
Sorry for the chatter. I used "gmake" instead of "make" and passed all 89
tests. That's a new one on me.
With apologies,
Murthy
-Original Message-
From: Murthy Kambhampaty
Sent: Friday, December 13, 2002 15:58
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject
Murthy Kambhampaty writes:
> Sorry for the chatter. I used "gmake" instead of "make" and passed all 89
> tests. That's a new one on me.
They're the same program, so this wasn't the cause. You probably
installed the files before you reran the regression tests, which typically
fixes this sort of p
On RedHat 8.0 (upgraded from Red Hat 7.2 with PostgreSQL 7.2.3), "make
check" gives the following error:
"/home/postgres/postgresql-7.3/src/test/regress/./tmp_check/install//usr/loc
al/pgsql/bin/pg_encoding: relocation error:
/home/postgres/postgresql-7.3/src/test/regress/./tmp_check/install//usr/
I tested database creation using v7.2.3 and I get the same pg_encoding error
if I give the "-E SQL_ASCII" option to createdb. If I don't give any
options, it creates the database just fine, and shows the encoding to be
SQL_ASCII. Moreover, issuing the query
"create database testmenow with template=
Murthy Kambhampaty <[EMAIL PROTECTED]> writes:
> "/home/postgres/postgresql-7.3/src/test/regress/./tmp_check/install//usr/loc
> al/pgsql/bin/pg_encoding: relocation error:
> /home/postgres/postgresql-7.3/src/test/regress/./tmp_check/install//usr/loca
> l/pgsql/bin/pg_encoding: undefined symbol: pg_
13 matches
Mail list logo
