Re: [GENERAL] Importing data w/ Unix timestamp

> insert into RealTable select uname, timestamp(abstime(timeinAsInt4)), > duration, etc from TempTable; Another side comment: afaik an explicit conversion to abstime is not required to go from Unix time to timestamp. So insert into RealTable select uname, timestamp

Re: [GENERAL] Comments with embedded single quotes

> Richard Harvey Chapman <[EMAIL PROTECTED]> writes: > > Are single quotation marks not allowed in comments? > > > test2=# /* John's cat is fat. */ > > test2'# > > test2'# '*/ > > test2-# ; > > ERROR: Unterminated quoted string > > test2=# > > They are, but it looks like psql's primitive parser

[GENERAL] pg_dump/load quoting.

Dear All, pg_dump is dumping INSERT commands that fail to reload. I'm putting stuff into a table using perl DBI; dbh->quote. A select shows a row like: 1047676 | 1047673 | CAB| breeders' associations pg_dump creates a line INSERT INTO "keywords" ("key","extkey","system","str") VALUES (1

Re: [GENERAL] NOTICE messages during table drop

"kurt miller" <[EMAIL PROTECTED]> writes: > Found these messages in the log this morning. > Can anyone explain why? > NOTICE: RegisterSharedInvalid: SI buffer overflow > NOTICE: InvalidateSharedInvalid: cache state reset Probably this indicates that you had another backend somewhere that had b

[GENERAL] NOTICE messages during table drop

Found these messages in the log this morning. Can anyone explain why? dropping tables for ucs... NOTICE: RegisterSharedInvalid: SI buffer overflow NOTICE: InvalidateSharedInvalid: cache state reset TIA, -km Get Your Priv

Re: [GENERAL] disk backups

Martijn van Oosterhout <[EMAIL PROTECTED]> writes: > Is there a better way? Here pg_dumping the DB takes over half an hour > (mainly because pg_dump chews all available memory). pg_dump shouldn't be a performance hog if you are using the default COPY-based style of data export. I'd only expect m

Re: [GENERAL] Importing data w/ Unix timestamp

[EMAIL PROTECTED] writes: > I want to copy in some data from a tab-delimited flat file, but one of the > columns that should translate into a datetime is in Unix timestamp format > (seconds since epoch). COPY isn't going to apply any datatype conversions for you. What you could do, though, is i

[GENERAL] Non-blocking LOCK

Hi. How can I request a lock in a non-blocking way? Instead of blocking until a certain lock can be acquired, I would like my client applications to give up immediately when a conflicting lock exists. My wish is that client applications locks the data while it is being edited, thus making the lo

Re: [GENERAL] disk backups

Stephen Lawrence Jr. wrote: > > I think the way most people do that is to have pg_dump or pg_dumpall make a > dump of the databases into the postgres directory each nite. That way, when > you do a full disk backup, the database dumps would be backed up as well. Is there a better way? Here pg_dum

[GENERAL] ORDBMS vs OODBMS

Hello folks I'm an engineering student and I would be very interested to learn the pros and cons between these two DataBases: - Versant : commercial OODBMS (Object-Oriented) - PostgreSQL : open source ORDBMS (Object-Relational) (Other DB like Oracle are ERDBMS and not ORDBMS if I guess right)

Re: [GENERAL] Importing data w/ Unix timestamp

[EMAIL PROTECTED] writes: > > I want to copy in some data from a tab-delimited flat file, but one of the > columns that should translate into a datetime is in Unix timestamp format > (seconds since epoch). > > The data should go into this table: > create table logins ( > uname varchar(100

[GENERAL] Importing data w/ Unix timestamp

I want to copy in some data from a tab-delimited flat file, but one of the columns that should translate into a datetime is in Unix timestamp format (seconds since epoch). The data should go into this table: create table logins ( uname varchar(100), timein datetime, duration int,