Re: [HACKERS] wierd AND condition evaluation for plpgsql

On Tue, 2002-05-28 at 16:09, Joel Burton wrote: > Actually, at least in some cases, PG does short-circuit logic: > joel@joel=# select false and seeme(); > joel@joel=# select true and seeme(); If seeme() returns NULL, shouldn't both SELECTs return NULL, and therefore not be short-circuit-able?

Re: [HACKERS] Our archive searching stinks

On Fri, 2002-06-21 at 17:07, Marc G. Fournier wrote: > > Can we find out why the email/news gateway drops messages? > > Email->News gateways aren't the best to start with, since they rely on far > too many variables ... main one coming to mind is if the news server is > down for any length o

Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am

In my book, schema support is a big thing, leading to rethink a lot of database organization and such. PostgreSQL 8 would stress this importance. -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus phone

Re: Release of v7.2.2 (Was: Re: [HACKERS] @(#)Mordred Labs ad...)

Builds and runs fine under HP/Compaq Tru64 aka Digital Unix aka OSF/1 (this is getting difficult...) version 4.0f/g using standard cc: template1=# SELECT version(); version PostgreSQL 7.2.2 on alphaev56-

Re: Changing Column Order (Was Re: [HACKERS] MySQL vs PostgreSQL.)

On Sat, 2002-10-12 at 11:37, Gavin Sherry wrote: > I cannot think of any reason why changing column order should be > implemented in Postgres. Seems like a waste of time/more code bloat for > something which is strictly asthetic. > > Regardless, I do have collegues/clients who ask when such a fe

Re: [HACKERS] Request for supported platforms

> Folks. start sending in those plaform reports, OS name and version > number please. DOESN'T WORK on Digital Unix/Tru64 4.0g, with both cc or gcc compiler. Using Compaq C V6.4-216 (dtk) on Digital UNIX V4.0G (Rev. 1530) Compiler Driver V6.4-013 (dtk) cc Driver: make[3]: Entering directory `/usr

Re: [HACKERS] Request for supported platforms

On Thu, 2002-10-31 at 18:53, Tom Lane wrote: > Evidently main.c needs "#include " added. I wonder what have changed since Beta2 that compiled fine... > Please add that and see if you get any further. Done, and now it builds (I've limited the test to native cc compiler for now). But it doesn't

Re: [HACKERS] Request for supported platforms

On Fri, Nov 01, 2002 at 10:22:42AM -0500, Tom Lane wrote: > I've committed fixes for the other issues too, so CVS tip should now > pass cleanly on your platform. I've built the snapshot from CVS tip and now the regression tests pass with both GCC 2.95.1 and Compaq C V6.4-216 (dtk) on Digital UNI

Re: [HACKERS] Request for supported platforms

On Tue, 2002-11-05 at 00:40, Bruce Momjian wrote: > Ports list updated: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html Please note that you have an entry for Digital Unix and one for Compaq Tru64 while in fact they are the same OS that went through a whirlwind of

[HACKERS] Re: RPM upgrade caveats going from a beta version to RC

Oliver Elphick wrote: > R = 82 > b = 98 This is a very small problem of having capital R and lowercase b that I believe can be taken into account in the development of 7.2. > As I suggested in another mail, let us switch to using even minor > numbers for releases and odd ones for development:

[HACKERS] Re: Truncation of char, varchar types

Nathan Myers wrote: > (Very long names may show up in machine- generated schemas.) Would > patches for this, e.g. to refuse to create a table with an impossible > name, be welcome? Yes. And throw in the picture also the length of sequences coming from SERIALs, etc. -- Alessio F. Bragadini

[HACKERS] Re: AW: Truncation of char, varchar types

Zeugswetter Andreas SB wrote: > Yes, iirc the only thing you are allowed to do is issue a warning, > but the truncation is allowed and must succeed. > (checked in Informix and Oracle) ? As much as I remember, Oracle raises an error. But it's been a few years since I last touched it, so maybe I'm

[HACKERS] Re: age() function documentation

Thomas Lockhart wrote: > The age() functions *preserve* the qualitative fields year and month. So > you see the difference in results: Why take away age()? I usually use it to check against INTERVALs? See: village=> select age(date '1999-05-17', date '1957-06-13') > '40 years'::interval; ?colu

[HACKERS] Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A

Thomas Lockhart wrote: > We had at least three reports of successful compilation on Tru64 4.0[dg] I can add up my experience of building on Tru64 4.0f (Compaq DS20E) without problems, using Digital's cc ./configure --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-maxba

[HACKERS] Re: RedHat/Postgres.pm Error

Allan C Huffman wrote: > May I please ask you guys a question about Postgres.pm. What is Postgres.pm? Talking about DBD::Pg or something completely different? -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus

Re: [HACKERS] Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A

> Mmmmhhh... Failed the int8 test Sorry, float8 -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking

Re: [HACKERS] Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A

Tom Lane wrote: > > I can add up my experience of building on Tru64 4.0f (Compaq DS20E) > > without problems, using Digital's cc > > Would you check whether things still work on your platform if CC becomes > "cc -std -ieee" rather than just "cc -std"? (Best way to check is to > alter src/templa

Re: [HACKERS] Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A

Tom Lane wrote: > Sounds good; could you check the regress tests too? Mmmmhhh... Failed the int8 test, but seems more a difference in the text of the error message. The others 75 were successful. diff attached -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services

[HACKERS] Comment about PostgreSQL on Epinions.com

While searching for some info and using google.com I came across I am the first to understand that the opinion in such a site is worthless and the guy seems not to understand anything about DBMSs but it's quite harsh anyway. --

[HACKERS] A problem with pg_dump?

I have a table with a FK on itself: in fact a record may depend on another table ("pig's ear" :-) I may run into a problem dumping/restoring using pg_dump, PostgreSQL 7.1.0. Here's a simplification of the table: provo=# SELECT version(); version ---

Re: [HACKERS] A problem with pg_dump?

Tom Lane wrote: > It's not much > harder than your given example to construct cases where dumping the rows > in OID order would be wrong too (just takes some UPDATEs). Yes, I figured out myself quickly. :-( > like you may have some pre-release copy of pg_dump that gets this wrong > (the commen

Re: [HACKERS] A problem with pg_dump?

Tom Lane wrote: > Current CVS pg_dump (grab the nightly snapshot if you don't use CVS, > or wait for 7.1.1 in a day or two) is alleged to be able to work > against a 7.0 database. Give it a try. That would be great, I had plans to wait for 7.1.1 anyway. Thanks -- Alessio F. Bragadini

Re: [HACKERS] A problem with pg_dump?

> Is it possible to use pg_dump 7.1 on a 7.0 database? Tried. Nope. -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- T

[HACKERS] A problem with new pg_dump

I've tried the pg_dump bundled in the new 7.1.1 release. I wanted to test its feature of dumping a 7.0.X database. Let's say I have database A running 7.1.1, B running 7.0.2. Both servers have the same database 'test', 'myview' is a view defined on both of them. I want to dump data only, being a

[HACKERS] Re: Outstanding patches

Tom Lane wrote: > But it's not really tracking the variable; with Ian's proposed > implementation, after > > create table foo(bar int4); > > create function fooey(foo.bar%type) ...; > > drop table foo; > > create table foo(bar in

[HACKERS] Re: ORDER BY Problem...

Severin Olloz wrote: > Why does Postgresql order the uppercase letters first? Do you have any LOCALE configuration in place? -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "I

[HACKERS] Re: FYI: status of native language support

Peter Eisentraut wrote: > language supported in the next release, this would be a good time to > gather up and volunteer for translation. I can help with Italian translation if no one else is volunteering (or coordinating a team) -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financi

[HACKERS] Re: OID wraparound (was Re: pg_depend)

Tom Lane wrote: > >> What's wrong with 64-bit oids (except extra 4bytes)? > > > Portability, mostly. > > Oh, there's one other small problem: breaking the on-the-wire protocol. So 8-byte-OID is for PostgreSQL 8? :-) -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services

[HACKERS] Re: Translators wanted

Peter Eisentraut wrote: > Please arrange yourselves with other volunteering speakers of your > language. Results should be sent to the pgsql-patches list. Any other Italian-speaking willing to do the job? I fear I won't have a lot of time to allocate even if I'm very interested. -- Alessio F.

[HACKERS] Re: Neutral Soil (OT)

August Zajonc wrote: > Perhaps Postgresql folks could start thinking of peace talk sites as well? I > recommand the tropics. Then all that's left is to find something to fight > about to justify a flight down to paradise. You are all welcome here in Cyprus. Monty too, he will find a lot of Swedi

[HACKERS] Re: unique index doesn't accept functions on fields

Domingo Alvarez Duarte wrote: > I'm trying create a unique index using more than one field and > applying a function in one field to achieve case insensitive > uniqueness but postgresql doesn't accept. > > create table a( > id int primary key, > id2 int not null, > name varchar(50), > un

[HACKERS] Re: Why is SERIAL a keyword?

Tom Lane wrote: > The only downside I can see to this is that it's currently possible to > use a user-defined type named "serial", if you are determined enough: > > create table foo ( > f1 serial, -- it's a serial column > f2 "serial",-- user-defined type

[HACKERS] Re: bugs - lets call an exterminator!

Tom Lane wrote: > it does seem like a lot of people > like Bugzilla. Might be worth at least a cursory look. We do use Bugzilla and I believe is a very good tool, which should fit nicely with the open development style of PostgreSQL community. New version is due in a few weeks and it's been alr

[HACKERS] Re: bugs - lets call an exterminator!

Vince Vielhaber wrote: > Everybody keeps saying bugzilla. What EXACTLY will bugzilla do for us > that would make me want to learn it and install it? BTW, the current > wheel was invented a year ago 'cuze nothing really fit what we needed. I believe the greatest advantage for the PostgreSQL is

Re: [HACKERS] How do I get a list of DB's or Tables with a postgres SQL statement?

Ron de Jong wrote: > I know there is some funtions in psql: > > \l(show databases) > \d(show tables) If you start psql with the -E option, it will show you which queries it makes to the internal tables to retrieve the backslash result. Then copying and customizing your own query is very

Re: [HACKERS] storing binary data

Christopher Kings-Lynne wrote: > What exactly is the advantage in using VIEWs? I get the impression that the > SELECT query it is based on is cached (ie. a cached query plan). I had the same impression but I've been told (with explanations) that the query plan for a view is not cached in any wa

Re: [HACKERS] FAQ error

Bruce Momjian wrote: > $newSerialID = nextval('person_id_seq'); > INSERT INTO person (id, name) VALUES ($newSerialID, 'Blaise Pascal'); > > Is this correct Perl? I don't see a nextval() function in Perl. Can > you call SQL server-side functions natively from Perl? Ofcourse not

[HACKERS] Re: [GENERAL] Slashdot and PostgreSQL

Hunter Hillegas wrote: > I don't think they're moving the actual Slashdot site to PostgreSQL... So do I. > I think other sites based on Slashcode wanted to be able to use PostgreSQL > though... That's what I will do as soon as possible, and I am trying to be involved as much as possible in the

Re: [HACKERS] Re: Sure enough, the lock file is gone

Florent Guillaume: > /tmp is for *temporary* files. Such a lock is not a temporary file, > it should go somewhere in /var, why not in /var/lib/pgsql/data ? /var/run ? -- Alessio F. Bragadini[EMAIL PROTECTED]

Re: [HACKERS] v7.4 Beta 1 fails regression on Digital Unix/Tru64 4.0

The first beta fails two regression tests on alphaev67-dec-osf4.0g, compiled by cc -std -std i.e. Compaq/HP Digital Unix/Tru64/name-of-the-day They are "join" (FAILED) and "random" (failed ignored). Attached is the regression diff. During configuration a warning stated that our version of Bison w

Re: [HACKERS] Beta2 Tag'd and Bundled ...

Hi, after Beta1 I'd reported problems in the regression tests under Digital Unix/Tru64. Unfortunately I had no time to report about my tests and to check Beta2 before now. Beta2 builds fine on Digital Unix 4.0G: template1=# SELECT version(); version -

Re: [HACKERS] Call for port reports

CC. OSF1 emily V4.0 1530 alpha (the existing port list has only a report for Tru64 5.X) -- Alessio Bragadini <[EMAIL PROTECTED]> APL Financial Services (Overseas) Ltd ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, plea

Re: [HACKERS] What do you want me to do?

uot;hack" applied to a specific version of Bugzilla. See http://bugzilla.mozilla.org/show_bug.cgi?id=98304#c57 IMHO it would be a good idea to help the Bugzilla team to finish the port in time for release 2.18 and join a very active tool. -- Alessio Bragadini <[EMAIL