I recently upgraded to 7.1.3. I was experimenting with a script to
export data from FoxPro into an SQL file and multiple data files. The
SQL file creates the tables, indexes, foreign keys, etc, and calls the
COPY command to load the data from the appropriate data files.
It appears, and I cou
"P. Dwayne Miller" <[EMAIL PROTECTED]> writes:
> It appears, and I could easily be mistaken, that the COPY command does
> not allow NULLs into a timestamp field, even though the field is defined
> to accept nulls.
Not sure what your problem is, but that's not it. Perhaps you've got a
problem w
Hi all,
Attached is a patch that adds support for specifying a location for
indexes via the "create database" command.
I believe this patch is complete, but it is my first .
Thanks
Jim
location.diffs
---(end of broadcast)---
TIP 2: you can
> On Tue, 11 Sep 2001, Bruce Momjian wrote:
>
> > >
> > > Wait until everyone is ready/finished with their existing projects ...
> > > this past week has thrown alot of turmoil into several lives that wasn't
> > > entirely unexpected, but sad nonetheless ...
> > >
> > > Let's do a poll on Friday
On Tue, 11 Sep 2001, Bruce Momjian wrote:
> >
> > Wait until everyone is ready/finished with their existing projects ...
> > this past week has thrown alot of turmoil into several lives that wasn't
> > entirely unexpected, but sad nonetheless ...
> >
> > Let's do a poll on Friday evening for who
> I know it can have an adverse effect on a mail server, is syslog going
> to give us any performance hits?
Yes. On some platforms (HP-UX at least) applications can stall ~2s
retrying if syslogd is not reading the messages written to its pipe.
syslogd also has a reputation for using too much C
On Mar 11 Sep 2001 02:07, Bruce Momjian wrote:
> > There was a discussion about --enable-syslog by default. What was the
> > consensus? I think this is a good one.
>
> Yes, I thought we decided it should be the default too.
There was a discusion about log rotation last week, so, where are we goin
On Tuesday 11 September 2001 06:14 pm, Martín Marqués wrote:
> There was a discusion about log rotation last week, so, where are we going?
> Pipe the output of postmaster to a log rotator like apaches logrotate, or
> are we going to use syslog and have the syslog log rotator do the rotation?
Both
It seems to be resonable to leave #define UNICODE_CONVERSION somewhere
(maybe in pg_config.h).
--
Tatsuo Ishii
> Peter Eisentraut wrote:
> >
> > Hannu Krosing writes:
> >
> > > I'm contemplating porting pg to PocketPC/WinCE platform and there the
> > > size does matter. And as WinCE is pure uni
> > Shall we correct the doc or is that a bug?
>
> Fix the docs...
Are you saying we should remove the whole chapter below from the docs?
--
Tatsuo Ishii
>5.2.1.3. Factorial
>
>This example illustrates an interesting result. Traditionally, the factorial operator
>is defined for integers only.
> Tatsuo Ishii writes:
>
> > There was a discussion about --enable-syslog by default. What was the
> > consensus? I think this is a good one.
>
> It would be a good one if we make the blind assumption that syslog()
> exists on all platforms. That is possible, but not guaranteed. (BeOS,
> QNX,
> Are you saying we should remove the whole chapter below from the docs?
Hmm. I wrote that :/
I vaguely recall some discussion of this topic (a few months ago?). I'm
not certain that the current behavior was an intended result of changes
in the "automatic coersion" algorithms, but I think it was
> Are you saying we should remove the whole chapter below from the docs?
Actually, it may be simply that we (now) implement factorial operators
for int8, int4, and int2. Not sure what previous releases implemented,
but perhaps it is just an issue of knowing which one should be used for
the operat
> > Are you saying we should remove the whole chapter below from the docs?
>
> Hmm. I wrote that :/
>
> I vaguely recall some discussion of this topic (a few months ago?). I'm
> not certain that the current behavior was an intended result of changes
> in the "automatic coersion" algorithms, but
Ludovic Pénet wrote:
> Hello,
>
> Reading the TO DO list, I found the following item:
> "Allow cursors to be DECLAREd/OPENed/CLOSEed outside transactions"
>
> I badly need this functionnality to interface postgres in my company
> database abstraction layer. Do you have any idea of when it should b
On Tue, 11 Sep 2001, Bruce Momjian wrote:
> > There was a discussion about --enable-syslog by default. What was the
> > consensus? I think this is a good one.
>
> Yes, I thought we decided it should be the default too.
I know it can have an adverse effect on a mail server, is syslog going
to giv
Wait until everyone is ready/finished with their existing projects ...
this past week has thrown alot of turmoil into several lives that wasn't
entirely unexpected, but sad nonetheless ...
Let's do a poll on Friday evening for who has stuff outstanding left, give
it until Monday for ppl to pop t
> > The x = NULL hack keeps biting people. Innocent people
> should not be
> > exposed to incorrect behaviour because of (supposed) MS Access
> > breakage. I strongly urge that we do one of the following:
> >
> > 1) Provide a tunable knob to turn this on (cf. KSQO)
> >
> > 2) Confine this to t
Tatsuo Ishii writes:
> There was a discussion about --enable-syslog by default. What was the
> consensus? I think this is a good one.
It would be a good one if we make the blind assumption that syslog()
exists on all platforms. That is possible, but not guaranteed. (BeOS,
QNX, Cygwin?)
The al
Hannu Krosing writes:
> I'm contemplating porting pg to PocketPC/WinCE platform and there the
> size does matter. And as WinCE is pure unicode platform there should be
> no need for 'conversions'.
The Unicode support is about 1 MB on disk. If you want to run a server
and you don't have the extr
"Joe Conway" <[EMAIL PROTECTED]> writes:
> I found a problem with PQescapeString (I think). Since it escapes
> null bytes to be literally '\0', the following can happen:
> 1. User inputs string value as "##" where ## are digits in the
> range of 0 to 7.
> 2. PQescapeString converts this to "\0##"
Jim Buttafuoco writes:
> will do.
While you're at it, at least the encoding parameter should be saved as
well. Take a peek at what pg_dumpall saves.
>
>
>
> > Jim Buttafuoco writes:
> >
> > > I am working a some patches to the code and I noticed that "pg_dump
> -C
> > > database" doesn't provi
Tatsuo Ishii writes:
> In comment.sgml:
>
> COMMENT ON AGGREGATE my_aggregate (double precision) IS 'Computes
> sample variance';
>
> this raises error. However,
>
> COMMENT ON AGGREGATE my_aggregate double precision IS 'Computes
> sample variance';
>
> works but looks strange syntax. Should we f
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> COMMENT ON AGGREGATE my_aggregate double precision IS 'Computes
>> sample variance';
>>
>> works but looks strange syntax. Should we fix the program or docs?
> I vote for fixing the program.
If we fix this, we should also change DROP AGGREGATE, wh
> Shall we correct the doc or is that a bug?
Fix the docs...
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> I have heard from Tom Lane that he will be out of town until Wednesday.
You may recall that I also have a substantial amount of work on
date/time issues which I would like to get in for beta. That is partway
done already, but not finished today.
I'm guessing that an additional week (or perhaps
Peter Eisentraut wrote:
>
> Hannu Krosing writes:
>
> > I'm contemplating porting pg to PocketPC/WinCE platform and there the
> > size does matter. And as WinCE is pure unicode platform there should be
> > no need for 'conversions'.
>
> The Unicode support is about 1 MB on disk. If you want to
(cough)
Could someone look at my 'select from cursor foo' patch...?
tnx
On Tue, 11 Sep 2001, Marc G. Fournier wrote:
>
> Wait until everyone is ready/finished with their existing projects ...
> this past week has thrown alot of turmoil into several lives that wasn't
> entirely unexpected, but
> (cough)
>
> Could someone look at my 'select from cursor foo' patch...?
Tom Lane has claimed that, plus the EXPLAIN patch. That's why they are
stuck in the patch queue. He has said he will take care of those and I
am sure he will.
--
Bruce Momjian| http://candle.p
>
> Wait until everyone is ready/finished with their existing projects ...
> this past week has thrown alot of turmoil into several lives that wasn't
> entirely unexpected, but sad nonetheless ...
>
> Let's do a poll on Friday evening for who has stuff outstanding left, give
> it until Monday fo
> > (cough)
> >
> > Could someone look at my 'select from cursor foo' patch...?
>
> Tom Lane has claimed that, plus the EXPLAIN patch. That's why they are
> stuck in the patch queue. He has said he will take care of those and I
> am sure he will.
I should have reported to you that the patch wa
I think we need this patch. Bytea encoding will be changed to accept
\000 rather than \0 for the same reason. I also agree that the libpq
enescaping of a C string doesn't need to deal with NULL like bytea does.
Your patch has been added to the PostgreSQL unapplied patches list at:
htt
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
> Hello,
>
> Attached patch is correction for 'doc/jdbc.sgml' of PostgreSQL 7.1.3.
>
> Correction content:
> * I revised
Hello,
Attached patch is correction for 'doc/jdbc.sgml' of PostgreSQL 7.1.3.
Correction content:
* I revised a mistake of type (copy and paste).
* I revised multiplicity of description.
Please review,
--
Ryouichi Matsuda
jdbc.sgml.diff
---(end of broadcast)-
34 matches
Mail list logo
