That explains it. In fact, the creates do not use double quotes, but the queries
do. I'll have to find a way to fix that.
Steve
>
> All identifiers are changed to lower case unless they are in
> double-quotes. If they use double-quotes in the creates, but not in the
> queries, you will have
> Try exporting the tables (including table creation stmts) to a text file and
> then ASCII ftping the file to the Unix Server to convert the CRLF and import
> using pgsql...The documentation has the commands to import files...
>
All identifiers are changed to lower case unless they are in
doub
Try exporting the tables (including table creation stmts) to a text file and
then ASCII ftping the file to the Unix Server to convert the CRLF and import
using pgsql...The documentation has the commands to import files...
- Original Message -
From: Stephen Birch <[EMAIL PROTECTED]>
To:
Having been suitable impressed by the "PostgreSQL ready for mission
critical apps" thread, I decided to bite the bullet and convert our
database from Interbase to PostgreSQL. Almost immediately I encountered
a puzzling problem. To make things easy, I am using the Borland "data
pump" on an NT mac
Hi folks,
"FATAL 1: palloc failure: memory exhausted" is the error and I have already
checked the FAQ and increased my memory allocation to 64M using limit/ulimit
as recommended.
moe: {2187} % limit
coredumpsizeunlimited
cputime unlimited
datasize131072 kbytes(actually a
At 11:48 AM 24-11-1999 -0500, Bruce Momjian wrote:
>> > would you like it to work? What parts are too complicated? If they only
>> > *appear* to be so, then this is a documentation deficiency, otherwise
we'd
>> > need to think about it.
>> I think the concept of user friendly design is universal.
I assume you are copying batches of data at the same time, so hardcoding in
the datetime wouldn't be a big problem right? Kludgy but should work.
Maybe if you did 'now' it might work. Or force it as 'now'::datetime.
Definitely not an expert- plenty to learn about SQL and Postgres, but since
no
Hi list,
Is it posible to read and write BLOBs to a PostgreSQL table using
the PostgreSQL ODBC driver?
Thanks in advance,
Guido Urdaneta
Hello,
I've noticed some previous postings about deadlocks in 6.4.2. At the
risk of being irritating, I'd like to ask if anyone has seen this
particular version of the problem: postmaster deadlocks leaving
multiple ZOMBIE children with something like the following in the log
file:
NOTICE:
Hi,
I've been using Postgres for a while for pretty simple schemas.
I'm now trying to clean things up, and start enforcing data integrity at
the SQL level, rather than the application level. I'm now running into the
following:
NOTICE: CREATE TABLE/FOREIGN KEY clause ignored; not yet implemen
ANNOUNCING:
UdmSearch Version 2.1.9
Full featured web search engine
WHAT IT IS:
UdmSearch is free SQL-based full-featured web search engine
software. You can use UdmSearch to build search engine
over HTTP, FTP, NTTP servers as well as over local files.
It supports several famous SQL backend
> > would you like it to work? What parts are too complicated? If they only
> > *appear* to be so, then this is a documentation deficiency, otherwise we'd
> > need to think about it.
> I think the concept of user friendly design is universal. There should be
> one button in the middle of the scre
On Wed, 24 Nov 1999, you wrote:
>
> Date: Tue, 23 Nov 1999 12:19:53 -0600 (CST)
> From: ^chewie <[EMAIL PROTECTED]>
> Subject: PL/pgsql or C/C++
>
> This is a general question expecting general answers. I've read the
> documentation concerning triggers and functions, as well as the
> documentat
On Wed, Nov 24, 1999 at 02:25:11PM +, Mark Jewiss wrote:
> Each time I vacuum (from either the script or the command line), I see
> things like:
>
> DEBUG: --Relation pg_indexes--
> DEBUG: Pages 0: Changed 0, Reapped 0, Empty 0, New 0; Tup 0: Vac 0,
> Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen
Hello,
Can't see an answer to this in the archives either
I'm automating the vacuum of each database I have every night using a cron
job on a perl script.
To tidy things up I want to put all of the messages received when
performing the vacuum into a log file, but cannot get this to work.
E
On Wed, 24 Nov 1999, Andrzej Mazurkiewicz wrote:
> Not using reference integrity tools (triggers, constrains) is in log-term a
> very dangerous practice.
Wait, we support both triggers and contraints though...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Syst
Hello,
An (admittedly quick) search through the list archives hasn't revealed
anything too similar to this problem, so hopefully someone here can
help
Have downloaded and unpacked version 6.5.3 of Postgresql to see the
differences between it and my current version (6.5.0). Running the
config
Not using reference integrity tools (triggers, constrains) is in log-term a
very dangerous practice.
- you cannot protect your data against by-passing your software simply with
psql;
- the more sophisticated scheme you use the more error prone it is; I am
very sceptical to solutions where somebo
18 matches
Mail list logo
