The extinction of a dolphin ... sign of things to come?
I've got a dolphin too (somebody's doing this on purpose ;):
http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=tucuxi&br=HEAD
A few hours ago I realized the vmware instance it's running in had
been suspended in a snapshot for the la
Hello,
triggers in PostgreSQL are cascading by default. From section 34.1.
of the 8.2 manual:
"If a trigger function executes SQL commands then these commands
may fire triggers again. This is known as cascading triggers.
There is no direct limitation on the number of cascade levels.
I
> Attached is a patch to get guppy green again (hopefully).
>
> The two new files go into src/interfaces/ecpg/test/expected
Hi,
I just wanted to mention that the latest release of OpenBSD i386
(4.0) is still broken too. So the ecpg-check failure would apply to
(at least) to 3.8, 4.0, and likely
On Fri, 12 Jan 2007 10:09:34 +0100 Joachim Wieland <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 12, 2007 at 09:29:36AM +0100, Stefan Kaltenbrunner wrote:
> > >ok, but then we have some hosts in the buildfarm that run the updated
> > >versions like zebra and spoonbill. In this case we can't decide on th
> > > i'm using debian sarge and when trying to compile 8.2beta3 got this
> > > fail...
> >
> > Just checked: no problems here on a stock 3.1.
> > What ./configure switches did you use?
> >
>
> ./configure --prefix=/usr/local/pgsql/pgsql
> --enable-debug--enable-cassert --enable-depend
>
Again,
> i'm using debian sarge and when trying to compile 8.2beta3 got this fail...
Just checked: no problems here on a stock 3.1.
What ./configure switches did you use?
Bye, Chris.
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
> > FWIW, there's a feature in CVS HEAD to instruct psql to try to use a
> > cursor to break up huge query results like this. For the moment I'd
> > suggest using COPY instead.
>
>
> That's sort of what I was afraid off. I am trying to get 100 million
> records into a text file in a specific or
> http://pgfoundry.org/docman/view.php/147/233/release82.zip
> is a zip file of a draft of the PostgreSQL 8.2 release and accompanying
> press kit. Please check if the technical details are correct, and get
> back to me with any corrections by Thursday.
Hi :)
I still see "Theo Scholossena
etting you insert 1000 records, then, at the end
say: "hah, all is rolled back becauase the 2nd record was invalid".
PG justly throws the exception immediately to let you know it's futile
inserting 998 more records.
I don't see a problem here.
Bye,
Chris.
--
Chris Mair
http
:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=guppy&dt=2006-09-05%
2010:02:05
Michael, if you want shell access to guppy, just contact me privately.
Warning: guppy too, is somewhat dated (1:10 hours for the make step) :/
Bye, Chris.
--
Chris Mair
http://www.1006.org
-
7;ve just upgraded guppy, the only other OpenBSD machine that builds
head to the latest buildfarm version.
I don't have any special malloc settings. When guppy finishes, we will
see what happens.
Bye, Chris.
--
Chris Mair
http://www.1006.org
---(end of broa
for applying this,
psql is faster now.
Thanks to all people that helped with this (lots...:)
Bye, Chris.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
t into the \g code path only.
Is it because presumably \g is used less often in existing psql scripts?
Bye, Chris.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
I don't know how the other uses factor in here, but I see it's called
at least twice more on average calls to SendQuery.
Bye,
Chris.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
psql need to scan the whole variables list
in GetVariable() for nothing).
Not sure if that's acceptable (I'd say yes, but then again, I'm
not a cycle counter type of programmer *cough* Java *cough* ;)...
Opinions?
Bye, Chris.
--
Chris Mair
http://www.1006.org
-
you perform lots of trivial queries
through psql. I'm going to benchmark something now and report back.
Anyway, regardless the benchmark, I feel it's somehow not clean to have
a variable introduce a difference between "\g" and ";".
[goes benchmarking...]
Bye, Chris.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
gt; > or some such.
\gc sounds like a good idea to me :)
(I must admit gc reminds me about 'garbage collector', which in a weired
way is related with what we're doing here... At least more related than
'Great Britain' ;)
> So add it as a modifyer to
ith \pset I'd have different places where I'd need to figure
out whether to do the cursor thing and I was a bit reluctant to add
stuff to existing code paths. Also the other \pset options are somewhat
orthogonal to this one. Just my two EUR cents, of course... :)
Bye, Chris.
--
Chris M
> > Patch with fix against current CVS is attached.
Forgot the attachment... soory.
--
Chris Mair
http://www.1006.org
diff -rc pgsql.original/doc/src/sgml/ref/psql-ref.sgml pgsql/doc/src/sgml/ref/psql-ref.sgml
*** pgsql.original/doc/src/sgml/ref/psql-ref.sgml 2006-08-17 16:50:58.000
th lists now, hope it's ok.
--
Chris Mair
http://www.1006.org
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message ca
monic value whatsoever ... isn't there
> some other name we could use?
True :)
Since buffer commands all have a single char I wanted a single char one
too. The "c" for "cursor" was taken already, so i choose the "u" (second
char in "cursor"). If somebo
Hi :)
powered by the great talk for newbie hackers by Neil Conway & Gavin
Sherry [1] at the anniversary summit I sneaked into the Code Sprint
and started working a bit on a Todo from Neil's Code Sprint Page:
"Add a psql option to have it submit SELECT queries via a cursor,
to avoid excessive
> but it is about 2Gb of data, so just putting a dump cleaned of personal
> data somewhere isn't really an option.
>
> I could arrange a dump without the diagnostics, in these 2 tables:
>
> system: < name | operating_system | os_version | compiler |
> compiler_version | architecture >
> build
> Thanks for the stats Andrew. Out of interest, can you easily tabulate
> the number of failures against OS?
Or, more generally, even put a dump of the DB (without personal infos
of course :) somewhere?
Bye, Chris.
PS: and don't say you're running it in MySQL ;)
---
> > I'd like to start working on the following TODO item:
> > Referential Integrity / Support triggers on columns
> >
> > Is somebody else already working on this?
>
> Sorry for not jumping in earlier. As Rob said, I am working on
> column-level support for triggers. I did not have my name addded
> > > I'd like to start working on the following TODO item:
> > > Referential Integrity / Support triggers on columns
> > >
> > > Is somebody else already working on this?
> >
> > No one, I think.
>
> Isn't this the REFERENCING clause? I think there was a partial patch
> submitted already for
Hello,
I'd like to start working on the following TODO item:
Referential Integrity / Support triggers on columns
Is somebody else already working on this?
Bye :)
Chris.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
On Sun, 2005-01-09 at 17:45, Peter Eisentraut wrote:
> Well, it does not readily explain that 'infinity' is rejected as invalid
> input syntax. You should get an overflow or some large value, at
> least.
>
> The relevant code is in src/backend/utils/adt/float.c.
You're right.
I had a look at
> > I've compiled 8.0 beta 1 on a R5900 V3.1 (a playstation 2) running
> > Linux (PS2 Linux 1) for portability testing.
> > ...
> > I'm wondering: would it be hard to fix the assembly spinlock code
> > for the R5900?
>
> According to the previous port report from Red Hat, the PS2 chip simply
> d
29 matches
Mail list logo
