>> Although...if COPY can handle the now() function, it should be able
>> to handle the current_user/current_timestamp without too much overhead.
Eh? COPY most assuredly does not handle the now() function, nor any
other function call.
It will accept 'now' --- no parens --- as an input for date
Herb,
> Right now I'm loading 1,500 test records in my largest table...but I
> don't
> want to do inserts...I'll stay with COPY and ignore the NULLS for
> now.
> In the future, however, I could be bulk loading up to 60,000 records.
> Of course, all records after that will be inserts, so perhaps
On Wed, 10 Oct 2001, Aasmund Midttun Godal wrote:
> I am sure this question has been answered in some form or another
> before, but I can't really find anything on exactly this issue.
>
> Are there any differences between varchar and text other than
>
> 1. varchar has limited size
> 2. varchar
I am sure this question has been answered in some form or another before, but I can't
really find anything on exactly this issue.
Are there any differences between varchar and text other than
1. varchar has limited size
2. varchar is SQL 92 text is not?
Especially regarding performance.
Or am
I sent with the wrong email first. sorry.
I can't find any docs / mails on this subject.
How can I restrict access to large objects.
1.) Based on users.
2.) Rules/triggers?
Thanx.
Aasmund Midttun Godal
[EMAIL PROTECTED] - http://www.godal.com/
+47 40 45 20 46
---
Title: VACUUM VERBOSE ANALYZE locking up?? Please help!
Ok it doesn't kill the whole backend, but VACUUM... comes
to a halt partway through and it's necessary to ^C out
of the transaction in psql. Sometimes trying again will
work, mostly that doesn't work. Restarting the backend
and then do
Hi all.
I have a problem with an application written in php.
I need to lock a record for update, and I use the following transaction:
BEGIN WORK;
//row1 is an indexed field
SELECT row1, row2 from table1 where row3 = NULL order by row1 FOR UPDATE
limit 1;
//fetch row1 in $myvar
UPDATE table1 set
