On Fri, 21 Jan 2005, Rao Kumar wrote:
Database System startup message
In postgres version 7.4.6, I notice that sometimes when the database starts
up, it outputs a log message such as 2005-01-18 14:44:13 FATAL: the
database system is starting up. Shouldn't this be LOG instead of FATAL
Below is logging information from a client-side SQL monitor, as well as what
I found in posgresqlhome/data/serverlog:
I this particular instance the offending quote is in the problem_desc field.
The value of problem_desc being Bob's Problem (double quotes excluded).
*** Client-Side SQL monitor
Hi Everybody,
I am working on a backup script for Postgres 8.0 online backups and
since i have to copy the whole pgdata directory , i am wondering after i
copy the pgdata directory can I run gzip or tar on the data directory ?
is it safe to do gzip or tar and I can safely restore the backups
Hi Guys,
I''ve been running pgbench tests for a while. I have one server set up
to run pgbench tpc tests (7.x). A new server that I just configured
with SUSE and 8.0.0 just gets killed even though it has the same memory
8 GB and it's a x86-64 box. The other one is Solaris full 64-bit.
On Mon, 2005-01-24 at 10:47, Pallav Kalva wrote:
Hi Everybody,
I am working on a backup script for Postgres 8.0 online backups and
since i have to copy the whole pgdata directory , i am wondering after i
copy the pgdata directory can I run gzip or tar on the data directory ?
is it
On Mon, 2005-01-24 at 10:48, Kavan, Dan (IMS) wrote:
Hi Guys,
I''ve been running pgbench tests for a while. I have one server set up
to run pgbench tpc tests (7.x). A new server that I just configured
with SUSE and 8.0.0 just gets killed even though it has the same memory
8 GB and
Scott Marlowe [EMAIL PROTECTED] writes:
On Mon, 2005-01-24 at 10:47, Pallav Kalva wrote:
I am working on a backup script for Postgres 8.0 online backups and
since i have to copy the whole pgdata directory , i am wondering after i
copy the pgdata directory can I run gzip or tar on the data
Hello, I have a following problem:
In short: I can't reload pg_dump --data-only dump (ver. 8.0) back to
the database, because the loading will violate ref. integrity.
The long story:
We have a PgSQL 7.2.5 database, and we like to bring only the data to
the PgSQL 8.0 system. So I did
On Mon, 2005-01-24 at 12:05, Tom Lane wrote:
Scott Marlowe [EMAIL PROTECTED] writes:
On Mon, 2005-01-24 at 10:47, Pallav Kalva wrote:
I am working on a backup script for Postgres 8.0 online backups and
since i have to copy the whole pgdata directory , i am wondering after i
copy the
Scott Marlowe [EMAIL PROTECTED] writes:
On Mon, 2005-01-24 at 12:05, Tom Lane wrote:
In the context of online backup operations, that advice isn't relevant
anymore ...
Really, is this an 8.0 thing then, that I can make file system backups
and expect them to be coherent, or did I misunderhear
Yes, they are both running on the same hardware - NAS.
On Mon, 2005-01-24 at 10:48, Kavan, Dan (IMS) wrote:
Hi Guys,
I''ve been running pgbench tests for a while. I have one server set
up to run pgbench tpc tests (7.x). A new server that I just
configured with SUSE and 8.0.0 just
On Mon, Jan 24, 2005 at 11:16:56AM -0700, Jani Averbach wrote:
What I am doing wrong? Or have I found an ordering bug with pg_dump
when you are doing --data-only dumps?
In a simple test I see the same ordering (alphabetical?) whether I
use --data-only or not. The schema+data dump succeeds
Jani Averbach [EMAIL PROTECTED] writes:
the following won't work:
4) Dump only data from just created 8.0 database:
pg_dump \
--data-only \
--column-inserts \
--use-set-session-authorization \
new_db new_db.data-only.dump
5)
Haron, Charles [EMAIL PROTECTED] writes:
*** Information From posgresqlhome/data/serverlog ***
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost.
On 2005-01-24 13:46-0500, Tom Lane wrote:
Jani Averbach [EMAIL PROTECTED] writes:
This will fail with lots of these kinds of errors:
ERROR: insert or update on table mytable
violates foreign key constraint mytable_myattr_fkey
Try it with --disable-triggers.
Thanks a
I hate to admit this publically, but I've been reading my results
backwards.
I was getting 100 tps on Solaris - postgres 64 bit and 300 tps on SUSE
postgres both x86-64.
So, 300 is better than 100 right? I was reading it backwards.
I was thinking 300 was the actual speed to process a certain
On Mon, 2005-01-24 at 13:19, Kavan, Dan (IMS) wrote:
I hate to admit this publically, but I've been reading my results
backwards.
I was getting 100 tps on Solaris - postgres 64 bit and 300 tps on SUSE
postgres both x86-64.
So, 300 is better than 100 right? I was reading it backwards.
I
17 matches
Mail list logo
