Sorry. I need to see the lines causing the error.
Looks like the problem is near here:
INSERT INTO product(title, summary, category, mfrcode, mfr, costprice,
rrprice, taxrate, weight) SELECT 'CF-37L/QD CASE for F-401s,x QD (not
original F-401QD)','FOR F-401,s,x, leatherette, no
strap','24081','8
Bruce,
I've put up a script for ftp that shows some wierd behaviour. This
script was created by hand, so it's possible that some errors are caused
by syntax errors (although I spent a while trying to find them without
success).
I think the point is that it is not recovering from/ reporting the er
Following this thread... just wondering is this a known problem of
updating from 6.3x to 6.4x or 6.5 ? or is this an isolated problem from
one user. We are looking to upgrade our postgresql 6.3.2 soon, (I think
we've been having some of the same problems described below ('backend
cache invalidat
>
> I've seen this problem too in 6.5 beta. I don't have a solution, but I'd
> just like to add my voice to say that this problem is real.
>
> Actually, I did have a kind of solution. If you dump proper insert
> statements into the dump and then run every insert in a separate
> process. Ugly but
I have had trouble on numerous occasions "undumping" a pg_dump. Below is
a perl script that I use as a pipe for undumping...hope it helps
.pg_undump.
#!/usr/bin/perl -p
# This script is a pipe that is used to break up PSQL dumps into pieces
# that are more manageable by the postmaster.
>
> AHH! The pgsql v6.3 backend has begun crashing horribly on me since I've
> added a few more database backed webpages (with messages like 'backend
> cache invalidation...').. I figured that upgrading to 6.4.2 would solve my
> problems.. But I can't upgrade! Things I've tried:
>
> * Using old
I've seen this problem too in 6.5 beta. I don't have a solution, but I'd
just like to add my voice to say that this problem is real.
Actually, I did have a kind of solution. If you dump proper insert
statements into the dump and then run every insert in a separate
process. Ugly but workable if t
On Sun, 30 May 1999, Oliver Elphick wrote:
> Gregory Maxwell wrote:
> >
> >AHH! The pgsql v6.3 backend has begun crashing horribly on me since I've
> >added a few more database backed webpages (with messages like 'backend
> >cache invalidation...').. I figured that upgrading to 6.4.2 woul
Gregory Maxwell wrote:
>
>AHH! The pgsql v6.3 backend has begun crashing horribly on me since I've
>added a few more database backed webpages (with messages like 'backend
>cache invalidation...').. I figured that upgrading to 6.4.2 would solve my
>problems.. But I can't upgrade! Things I
AHH! The pgsql v6.3 backend has begun crashing horribly on me since I've
added a few more database backed webpages (with messages like 'backend
cache invalidation...').. I figured that upgrading to 6.4.2 would solve my
problems.. But I can't upgrade! Things I've tried:
* Using old pg_dumpall -z
At 01:06 +0300 on 29/05/1999, JT Kirkpatrick wrote:
> can i change the owner of tables, indexes, etc in postgres??? from a bash
> prompt of course postgres owns everything. but when in psql you type \dt,
> i'd like for another person to own the tables. any way to do so??
Log into psql as tha
11 matches
Mail list logo
