Hi
I have recently migrated my database from MS Sql
Server to postgresql 7.3.1. In MS SQL SERVER, it is
very easy to set the lock time equals to zero on ROW
LEVEL. So that if some other user try to access the
same data, he/she will get the error immediately. I
have tried to run the same code throug
Hi,
I saw I can define a table that specifies a ON UPDATE CASCADE for a Foreign Key.
I have a lot of tables with FK´s, and a lot of others with others FK\'s for the firts
ones, and so on, and I haven´t defined the ON CASCADE clause on the FK´s tables.
Now I need to update a primary key on the \
Tom,
User was able to recreate the problem, but this time only on table got
duplicated 'gui_config'. So here is the info you wanted:
select ctid,xmin,xmax,oid,* from pg_class where relname = 'gui_config';
ctid | xmin | xmax | oid | relname | reltype | relowner | relam |
relfilenode | relp
Hi all,
I have a database cluster running on PostgreSQL 7.1.3 compiled from source, on
Debian Linux. I want to upgrade the cluster to PostgreSQL 7.3.x.
In order to get the data over, I ran: PGUSER=postgres
/usr/local/pgsql/bin/pg_dumpall > survey1.sql on the production machine
running 7.1.3.
> I got lots of errors about "Invalid command \N" in the COPY xxx FROM
> statements, and most of the tables were completely empty.
Try dumping with -d or -D:
-d, --insertsdump data as INSERT, rather than COPY, commands
-D, --column-inserts dump data as INSERT commands with column
Geoffrey Wossum <[EMAIL PROTECTED]> writes:
> I then took that file over to test machine running PostgreSQL 7.3.1,
Er, how did you copy the file over exactly?
This smells to me like it could be a newline-formatting problem (COPY is
pretty picky about its newlines). If you passed the file through
-- Forwarded Message --
Subject: Re: [ADMIN] Problems upgrading from 7.1.3
Date: Wednesday 05 February 2003 01:39 pm
From: Geoffrey Wossum <[EMAIL PROTECTED]>
To: "Bjoern Metzdorf" <[EMAIL PROTECTED]>
On Wednesday 05 February 2003 11:36 am, you wrote:
> > I got lots of errors
On Wednesday 05 February 2003 01:12 pm, Tom Lane wrote:
> Er, how did you copy the file over exactly?
scp
> This smells to me like it could be a newline-formatting problem (COPY is
> pretty picky about its newlines). If you passed the file through
> anything that might choose to convert Unix ne
Dear list:
I need to move all databases from one fiscal server to other,
but, the
main problem I have is: I can't dump databases, for internal problems
from hdd. My question is, so, how can rescue all databases in 'cp
command' way in posgresql version 7.0 ?
Needing to know:
Hi all,
Just wondering about how useful the vacuumdb functionality is for a database
that pretty much only ever gets inserts/selects.
I've got a database that is intended for next-to-no deletion of records, which
is where I see the vacuum facility mostly intended for. I.e., while there'll be
the
Tom Lane wrote:
I tried to replicate this, and could not: the restore went into the
expected database. (But I did notice that pg_restore needed to be
explicitly told -Ft, which seems less than bright of it.) Are you
sure those are the exact commands you issued? Were you using the 7.3
versions
Geoffrey Wossum <[EMAIL PROTECTED]> writes:
> On Wednesday 05 February 2003 01:12 pm, Tom Lane wrote:
>> This smells to me like it could be a newline-formatting problem (COPY is
>> pretty picky about its newlines).
> [ Nope ]
Drat, another perfectly good theory down the drain.
> Bjoern suggested
Preston <[EMAIL PROTECTED]> writes:
> Just wondering about how useful the vacuumdb functionality is for a database
> that pretty much only ever gets inserts/selects.
> I've got a database that is intended for next-to-no deletion of
> records, which is where I see the vacuum facility mostly intende
Quoting Tom Lane <[EMAIL PROTECTED]>:
> Preston <[EMAIL PROTECTED]> writes:
> > Just wondering about how useful the vacuumdb functionality is for a
> > database
> > that pretty much only ever gets inserts/selects.
>
> > I've got a database that is intended for next-to-no deletion of
> > records,
Preston <[EMAIL PROTECTED]> writes:
> Does that transaction load include selects?
Yes.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Dear Milist,
Somebody please give me more
explanation about
using "Update" syntax with cursor. I've
seen this
on manual of postgre(sql-update.html). Here
it is
the example;
UPDATE table SET column
= expression [,
...] WHERE CURRENT OF
cursor
But there's no
further clear
Hello everybody!
We have a problem with VACUUM FULL and the our PostgresSQL is very slow.
On the try run the vacuum command, its returns:
NOTICE: Child itemid in update-chain marked as unused - can't continue repair_frag
ERROR: No one parent tuple was found
vacuumdb: vacuum nube failed
I t
Marcelo Pereira Tada <[EMAIL PROTECTED]> writes:
>> NOTICE: Child itemid in update-chain marked as unused - can't continue repair_frag
>> ERROR: No one parent tuple was found
Try updating to 7.2.4; that should fix this.
regards, tom lane
---(end
18 matches
Mail list logo
