At 01:36 31/03/01 -0500, Tom Lane wrote:
>
>which is OK as far as the field set goes, but it loses the additional
>DEFAULT and NOT NULL information for the child table. Any thoughts on
>the best way to fix this?
>
Can pg_dump easily detect overridden attrs? If so, we just treat them as
table att
Philip Warner <[EMAIL PROTECTED]> writes:
> Not a squawk as such, but does this have implications for pg_dump?
Good point. With recently-committed changes, try:
regression=# create table p1 (f1 int default 42 not null, f2 int);
CREATE
regression=# create table c1 (f1 int, f2 int default 7) inhe
At 15:49 31/03/01 +1000, Philip Warner wrote:
>
>(TOC2 > TOC1)
>iff (Max(TOC2.OID, TOC2.DEPS) > Max(TOC1.OID, TOC1.DEPS))
> OR (Max(TOC2.OID, TOC2.DEPS) = Max(TOC1.OID, TOC1.DEPS)
> And TOC1.OID = Max(TOC2.DEPS)
> )
>
>Where D
At 14:55 30/03/01 -0500, Tom Lane wrote:
>
>A more promising idea
>is to hack function creation so that the OID assigned to the function
>is lower than the OIDs assigned to any shell types created when the
>function is defined.
This seems hard; would it be better to have the CREATE TYPE use a new
At 12:10 30/03/01 -0500, Tom Lane wrote:
>
>Comments? I'm going to implement and commit this today unless I hear
>loud squawks ...
>
Not a squawk as such, but does this have implications for pg_dump?
Philip Warner
> Well, once I figured out a few things about how to use the Unix part
> of MacOS X it seemed to work without a hitch in the regression
> testing. I need to figure out how to make the system start it up
> automatically at boot time still, but then I need to figure out how
> to do double sided pri
> I still don't see an entry for Linux 2.4.x
My (uncommitted) updates to the real list show 2.4.2 in the comments
section. I may remove all mention of versions, since it seems that most
released versions of x86 Linux run PostgreSQL successfully.
Comments?
- Thomas
> > Un
> Hi
>
> Regarding my previous post, I just successfully created a unique index on
> pg_shadow. DON'T DO THIS!!!
> ---
> CREATE UNIQUE INDEX shadow_index ON pg_shadow (usename)
> ---
> I couldn't create at pg_shadow_index as the pg prefix is reserved for
> system tables.
>
> This BRO
> -Original Message-
> From: Mikheev, Vadim [mailto:[EMAIL PROTECTED]]
>
> > > It is intuitive. The bug was iirc, that you saw 2 versions
> > > of the same row in the second select statement (= 2 rows
> > > returned by second select).
> >
> > I think we should be extremely wary of assum
I never liked the fact that the TODO web page pulls up a flat file copy
of the TODO.detail mailbox file.
I hacked together a little script that automatically MHonarc's
the TODO.detail file and displays it to the user.
You can see it if you go to main TODO web page:
http://www.postgresql
On Sat, Mar 31, 2001 at 12:02:35PM +1200, Franck Martin allegedly wrote:
> I still don't see an entry for Linux 2.4.x
>
> Cheers.
This should fix that:
==
All 76 tests passed.
==
rm regress.o
make[2]: Leaving directory `/usr/exp/tmp/postgresql-7.1RC1/sr
if i use type "crypt", the backend assumes that the client is
handing it an already encrypted passwd, and then compares it to an encrypted
version of pg_shadow->passwd.
and if i use type "password filename", the backend assumes a clear text
password from the client, and then compares an encrypte
I still don't see an entry for Linux 2.4.x
Cheers.
Thomas Lockhart wrote:
> Unreported or problem platforms:
>
> Linux 2.0.x MIPS 7.0 2000-04-13 (Tatsuo has lost machine)
> mklinux PPC750 7.0 2000-04-13, Tatsuo Ishii
> NetBSD m68k7.0 2000-04-10 (Henry has lost machine)
> NetBSD Sp
> I have a Cobalt 2.0.x MIPS box that is currently compiling the latest CVS
> of PostgreSQL ... I'll let you know in a few hours how it went.
Great!
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
On Fri, Mar 30, 2001 at 11:05:53PM +0200, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > 3. The new column will have a default value if any of the combined
> > column specifications have one. The last-specified default (the one
> > in the explicitly given column list, or the rightmost parent t
On Fri, Mar 30, 2001 at 12:10:59PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > The O-O principle involved here is Liskov Substitution: if the derived
> > table is used in the context of code that thinks it's looking at the
> > base table, does anything break?
>
> I propo
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> 4. All relevant constraints from all the column specifications will
>> be applied. In particular, if any of the specifications includes NOT
>> NULL, the resulting column will be NOT NULL. (But the current
>> implementation does not support inherita
Tom Lane writes:
> 3. The new column will have a default value if any of the combined
> column specifications have one. The last-specified default (the one
> in the explicitly given column list, or the rightmost parent table
> that gives a default) will be used.
This seems pretty random. It wo
Anything dependent upon the original function in your example is busted
anyhow, regardless of a dump/reload:
CREATE function test() returns int4 AS 'SELECT 1' LANGUAGE 'SQL';
CREATE
SELECT test()
test
--
1
(1 row)
CREATE VIEW test_view AS SELECT test();
CREATE
SELECT * FROM test_vie
> A more promising idea is to hack function creation
> so that the OID assigned to the function is lower
> than the OIDs assigned to any shell types created
> when the function is defined. Or we could try to
> hack pg_dump to fix this, but that doesn't seem
> appetizing.
Requiring OID ordering w
> I can think of a couple of ways to deal with this, the simplest being
> to say "don't do that" --- ie, define widget_in with result type
> "opaque" rather than "widget". That's pretty ugly and will likely
Why is it ugly? Why not update RETURNS type for XXX_in function when
creating type?
> br
> > This will take thought, research and discussion. A quick fix is the
> > last thing that should be on our minds.
>
> From my latest tests( see following post), I tend to agree,
> that this is extremely sensitive :-(
> I do however think that Vadim's patch description was the
> correct thing
On Fri, 30 Mar 2001, Dominic J. Eidson wrote:
> I have a Cobalt 2.0.x MIPS box that is currently compiling the latest CVS
> of PostgreSQL ... I'll let you know in a few hours how it went.
Compiled fine, and passed all but the geometry regression test:
[root@web-cache regress]# more regression.o
Tricia Holben of Great Bridge just pointed out to me a rather nasty
problem that's exposed by trying to pg_dump and reload the regression
test database. The regression tests include
CREATE FUNCTION widget_in(opaque)
RETURNS widget
AS '/home/postgres/pgsql/src/test/regress/regress.sl'
LA
> > It is intuitive. The bug was iirc, that you saw 2 versions
> > of the same row in the second select statement (= 2 rows
> > returned by second select).
>
> I think we should be extremely wary of assuming that we have a clear
> characterization of "what the bug is", let alone "how to fix it".
> > Wow, I see. I never suspected it did that too. :-) Seems I don't need
> > to write anything, except perhaps add group capabilities to pgaccess.
>
> Isn't phpPgAdmin yet another tool of this type? I haven't tried it myself,
> (no need, myself being the only user...) but the web page
> (http
> > > I doubt if it's a bug of SELECT. Well what
> > > 'concurrent UPDATE then SELECT FOR UPDATE +
> > > SELECT' return ?
> >
> > I'm going to add additional check to heapgettup and
> > heap_fetch:
>
> SELECT seems to be able to return a different result
> from that of preceding SELECT FOR UPDATE
> The Hermit Hacker writes:
>
> > Just a heads up for anyone that might have something outstanding ... I'm
> > going to package her early evening (~18:30AST) and announce it to both
> > pgsql-hackers and pgsql-announce when done ...
> >
> > Once RC2 goes out, its meant to be a "this is what we'd
On Fri, 30 Mar 2001, Peter Eisentraut wrote:
> The Hermit Hacker writes:
>
> > Just a heads up for anyone that might have something outstanding ... I'm
> > going to package her early evening (~18:30AST) and announce it to both
> > pgsql-hackers and pgsql-announce when done ...
> >
> > Once RC2 go
On Fri, 30 Mar 2001, Mathijs Brands wrote:
> On Fri, Mar 30, 2001 at 03:17:06PM +, Thomas Lockhart allegedly wrote:
> > And here are the up-to-date platforms; thanks for the reports:
>
>
>
> > Solaris 2.7 Sparc 7.1 2001-03-22, Marc Fournier
>
> Marc, was this done without unix sockets?
nop
( I deleted the email accidentially)
I have a Cobalt 2.0.x MIPS box that is currently compiling the latest CVS
of PostgreSQL ... I'll let you know in a few hours how it went.
# uname -a
Linux web-cache 2.0.34C52_SK #1 Tue Nov 30 18:14:40 PST 1999 mips unknown
--
Dominic J. Eidson
On Fri, Mar 30, 2001 at 03:17:06PM +, Thomas Lockhart allegedly wrote:
> And here are the up-to-date platforms; thanks for the reports:
> Solaris 2.7 Sparc 7.1 2001-03-22, Marc Fournier
Marc, was this done without unix sockets?
Mathijs
--
It's not that perl programmers are idiots, it's
[EMAIL PROTECTED] (Nathan Myers) writes:
> The O-O principle involved here is Liskov Substitution: if the derived
> table is used in the context of code that thinks it's looking at the
> base table, does anything break?
Good point. That answers my concern about how to handle typmod: an
applicati
The Hermit Hacker writes:
> Just a heads up for anyone that might have something outstanding ... I'm
> going to package her early evening (~18:30AST) and announce it to both
> pgsql-hackers and pgsql-announce when done ...
>
> Once RC2 goes out, its meant to be a "this is what we'd release if doc
I can confirm with current sources:
test=> CREATE UNIQUE INDEX shadow_index ON pg_shadow (usename);
CREATE
test=> select * from pg_shadow;
ERROR: Index 'pg_shadow_sysid_index' does not exist
test=> \q
$ psql test
psql: FATAL 1: Index 'pg_
This is fixed in current 7.1RC1 sources.
> Hi guys,
>
> I don't want to do a patch for a one character error. Yet, that's a HUGE
> error and it really needs to be fixed.
>
> Once you have a pg_database file which is over 1 page, it CRASHES. That's
> what it did on me. Yes! I have many database
> If I remember correctly, UPDATE establishes a lock on the affected rows,
> which will block another UPDATE on the same rows for the duration of the
> transaction. If that's true, shouldn't I be able to achieve my desired
> behavior by removing the initial as follows:
>
> create function ne
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> It is intuitive. The bug was iirc, that you saw 2 versions of the same row
> in the second select statement (= 2 rows returned by second select).
I think we should be extremely wary of assuming that we have a clear
characterization of "what th
> Bruce Momjian writes:
>
> > I have started coding a user/group administration tool that allows you
> > to add/modify/delete users and groups. I should have something working
> > in a week. I will look similar to my pgmonitor tool.
>
> Pgaccess already does part of this. If you're going to w
> > It is intuitive. The bug was iirc, that you saw 2 versions of the same row
> > in the second select statement (= 2 rows returned by second select).
>
> I think we should be extremely wary of assuming that we have a clear
> characterization of "what the bug is", let alone "how to fix it".
> T
> Yep. We have many other MIPS (ONYX Crimson, , ONYX, Challenge, Indy w/ IRIX
> 6.2, 6.5, etc.), Alpha and Sparc platforms if there are some others that need
> testing (How about NetBSD on NeXT?).
All of these are interesting to help others decide whether their
particular machine is supported.
Bruce Momjian writes:
> I have started coding a user/group administration tool that allows you
> to add/modify/delete users and groups. I should have something working
> in a week. I will look similar to my pgmonitor tool.
Pgaccess already does part of this. If you're going to write it in Tcl
Unreported or problem platforms:
Linux 2.0.x MIPS 7.0 2000-04-13 (Tatsuo has lost machine)
mklinux PPC750 7.0 2000-04-13, Tatsuo Ishii
NetBSD m68k7.0 2000-04-10 (Henry has lost machine)
NetBSD Sparc 7.0 2000-04-13, Tom I. Helbekkmo
QNX 4.25 x86 7.0 2000-04-01, Dr. Andrea
> To the rest on the list:
> Try the above example by adding a lock between the two lines:
>
> create function nextid( varchar(32)) returns int8 as '
> update idseq set id = id + 1 where name = $1::text;
> select * from lock1;
> select id from idseq where name = $1::text for update;
Maurizio writes:
> configure:6840: checking test program
> configure:6849: gcc -o conftest.map conftest.c -lz -lunix -lresolv -lPW -lgen
>-lBSD -lcompat -lld -ldld -llc -lIPC -lipc -lnsl -lsocket -ldl -lm -lbsd -lsfio
>-lunix 1>&5
> cc warning: cc: cannot find library 'resolv'
> cc warning
This seems to work for me. I used the snapshot from 3/28 on Solaris 8
SELECT service, count(*) AS GebruikersAantal
FROM tbtrouble GROUP BY service;
service | gebruikersaantal
---+--
Service 1 |2
Service 3 |2
Service 4 |
Matthew writes:
> semi related to this, I have always thought that the way postgresql
> handles the deletion of users and groups to be flawed. If I create a user,
> grant permissions on a table and then drop the user, permissions now exist
> on that table for a user that does not exist.
U
Hi,
I've written an extension to PGSQL that in some cases has to abort the
current transaction. It calls AbortCurrentTransaction() in that case, but
the problem is that the client doesn't get notified.
Is there a way to detect such an abort, or do I have to make a
modification the the client li
At 11:06 PM 3/28/01 -0500, Tom Lane wrote:
>Mark Knox <[EMAIL PROTECTED]> writes:
>> I don't think this solution would be valid on many other platforms.
>
>Au contraire --- the ARM is the first platform I've heard of that does
>not think sizeof(ItemPointerData) is 6. Else we'd have seen this
>reg
hi,
I come back in office after a long period out for
work.
Yesterday I have downloaded the last
snapshot.
When I execute configure I have an error compiling
conftest.
The last version I have checked was 7.1 b3 and all
works fine.
Attached is the config.log file.
Has someone any sugge
Hi guys,
I don't want to do a patch for a one character error. Yet, that's a HUGE
error and it really needs to be fixed.
Once you have a pg_database file which is over 1 page, it CRASHES. That's
what it did on me. Yes! I have many databases or rather, I often destroy
my databases to regenerate t
On Tuesday 27 March 2001 15:14, Tom Lane wrote:
> Forest Wilkinson <[EMAIL PROTECTED]> writes:
> > session1<< create function nextid( varchar(32)) returns int8 as '
> > session1<< select * from idseq where name = $1::text for update;
> > session1<< update idseq set id = id + 1 where name = $1:
> > > I doubt if it's a bug of SELECT. Well what
> > > 'concurrent UPDATE then SELECT FOR UPDATE +
> > > SELECT' return ?
> >
> > I'm going to add additional check to heapgettup and
> > heap_fetch:
> >
>
> SELECT seems to be able to return a different result
> from that of preceding SELECT FOR U
> On Tue, Mar 27, 2001 at 08:08:47PM -0500, Tom Lane wrote:
> Mathijs Brands <[EMAIL PROTECTED]> writes:
> > No luck :( Tests still randomly crash. (This is an Ultra 10 machine.)
>
> How about if you change the pg_regress script to use TCP connections?
> (Look for the bit that forces unix_sockets
Hi
I am new to PostgreSQL, and I would like to install it on a Linux box. I
wish to create and edit databases programmatically using Java. My problem is
that I don't know where to get the drivers for PostgreSQL. I will be glad if you
could refer me to a few sites that you know of.
regard
Dear all,
please excuse me for posting out of the blue (I am no longer
subscribed) but I have been asked by my colleagues to send a message
since I've pretty much been hacking at this problem all day.
To summarise the issue briefly we were very confused regarding the SET
TIMEZONE command which b
Subject: Importing data from Informix to PostgreSQL.
Error in the date field (WITH NULL value)
Hello!
I'll try to explain my little problem. Well, I have this table
create table mytable
( codice char(16) not null,
dt_inizio date,
dt_finedate,
tipo_operaz
On Tue, 27 Mar 2001 09:57:45 -0500 (EST), Bruce Momjian alluded:
>
> We just fixed that yesterday. Can you grab the most recent CVS and give
> it a try?
Yep. We have many other MIPS (ONYX Crimson, , ONYX, Challenge, Indy w/ IRIX
6.2, 6.5, etc.), Alpha and Sparc platforms if there are some
"Mikheev, Vadim" wrote:
>
> > > >> I assume this is not possible in 7.1?
> > > >
> > > >Just looked in heapam.c - I can fix it in two hours.
> > > >The question is - should we do this now?
> > > >Comments?
> > >
> > > It's a bug; how confident are you of the fix?
>
> 95% -:)
>
> > I doubt if it'
On Fri, Mar 30, 2001 at 11:07:25AM +0100, Pete Forman allegedly wrote:
> I've done a quick survey of the Suns available to me to see whether
> sendmail updates the ps display. The summary is:
>
>1) Require "/usr/ucb/ps w" at least. /usr/bin/ps has no options
> that I can find to displ
Bruce Momjian writes:
> > Tom Lane writes:
> > The consequence should be:
> >
> > 1. check if sendmail works with /usr/bin/ps
> >
> > 2. a) if yes, figure out what got lost in PostgreSQL
> >
> > 2. b) if no, make the Solaris case in ps_status.c use the BSD
> > approach
>
> [ I
hi,
Sorry if you receive this message again . I just sent it yesterday
with attached the config file but probably was too large.
I come back in office after a long period out for
work.
Yesterday I have downloaded the last
snapshot.
When I execute configure I have an error compiling
c
62 matches
Mail list logo
