On Tue, Jan 04, 2005 at 11:51:54PM -0600, Jaime Casanova wrote:
> create view vfoo as select oid, * from foo;
> ...
> create rule insrule as on insert to vfoo
> do instead
> insert into foo(id, name) values (new.id, new.name);
> ...
> insert into vfoo values(1, 'test1');
> ERROR: invalid input sy
Hi,
i forgot to mention the version it's pgsql-8.0.0rc3.
freshly installed.
regards,
Jaime Casanova
_
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
--
Hi,
i was doing some tests and found out this:
create table foo (
id serial not null primary key,
nametextnot null
);
NOTICE: CREATE TABLE will create implicit sequence
"foo_id_seq" for serial column "foo.id"
NOTICE: CREATE TABLE / PRIMARY KEY will create
i
Hi All,
We are
running postgresql version 7.3.4. Due to some problem, i was asked to restart
the postgres. when i try to restart the postgres i did not start and gave the
following error message.
Log : database system was interrupted being
in recovery at 2005-01-04 20:41:00 UTC
On Tue, 4 Jan 2005, Serguei A. Mokhov wrote:
On Tue, 4 Jan 2005, Peter Eisentraut wrote:
With the 8.0 release around the corner, this is as good a time as ever
to send in the last translation updates. If your files are not in CVS
right now, I don't have them, so please send them again in this case
Hi all
best wishes, and happy new year ! :) :)
I implement a new type of join called "Double Pipelined Hash Join".
This type of join requires 2 hash tables; one for the left (outer) and
one for
the right(inner) relation. At the execution phase one (or more)
tuple(s) from the inner relati
(cc'ing -hackers)
Karel Zak wrote:
I think command status is common and nice feedback for client. I think
it's more simple change something in JDBC than change protocol that is
shared between more tools.
There is a bit of a queue of changes that would be nice to have but
require a protocol version
Tom, Merlin,
> It's not fundamentally different from single-column indexes. The only
> aspect of a btree index that requires any knowledge about the content of
> index entries is the "compare two index entries for lesser, equal, or
> greater" operation. For that, we just compare the first column
Josh Berkus writes:
> I've been poking around the indexing code, and I really don't understand the
> page structure and splittng/branching for multi-column BTree indexes.
It's not fundamentally different from single-column indexes. The only
aspect of a btree index that requires any knowledge ab
On Tue, 4 Jan 2005, Peter Eisentraut wrote:
> With the 8.0 release around the corner, this is as good a time as ever
> to send in the last translation updates. If your files are not in CVS
> right now, I don't have them, so please send them again in this case.
A batch of Russian translation upda
> Folks,
>
> I've been poking around the indexing code, and I really don't
understand
> the
> page structure and splittng/branching for multi-column BTree indexes.
> I've
> looked in a couple DB textbooks to get a theoretically underpinning of
the
> structure of multi-column indexes, but none of t
With the 8.0 release around the corner, this is as good a time as ever
to send in the last translation updates. If your files are not in CVS
right now, I don't have them, so please send them again in this case.
Thanks.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
Folks,
I've been poking around the indexing code, and I really don't understand the
page structure and splittng/branching for multi-column BTree indexes.I've
looked in a couple DB textbooks to get a theoretically underpinning of the
structure of multi-column indexes, but none of the ones I'
ARM platform fails the "point" test see below.
parallel group (13 tests): text name char boolean varchar oid int8 int2 float4
int4 float8 bit numeric
boolean ... ok
char ... ok
name ... ok
varchar ... ok
text
what failure. both my MIPS and MIPSEL system are reporting OK on the builds.
The ARM failed only the "point" test.
It looks like a rounding error (ARM doesn't have a build in fp unit)
-- Original Message ---
From: Peter Eisentraut <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc
Am Dienstag, 4. Januar 2005 14:53 schrieb Jim Buttafuoco:
> I have both a MIPS and MIPSEL in the buildfarm. i have also reported a
> good build on a arm (Debian/Sarge/Netwinder) (not yet in the build farm)
Well, a build with regression test failures is not "good", in particular when
it is a regr
I have both a MIPS and MIPSEL in the buildfarm. i have also reported a good
build on a arm (Debian/Sarge/Netwinder)
(not yet in the build farm)
-- Original Message ---
From: Peter Eisentraut <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Robert Treat <[EMAIL PROTECTED]>, pgsql
On Mon, 2005-01-03 at 19:14 -0500, Bruce Momjian wrote:
> Simon Riggs wrote:
> > Here's my bgwriter instrumentation patch, which gives info that could
> > allow the bgwriter settings to be tuned.
>
> Uh, what does this do exactly? Add additional logging output?
>
Produces output like this...
D
18 matches
Mail list logo
