Re: [HACKERS] bug or feature, || -operator and NULLs

On Wednesday 18 October 2006 10:35, Lukas Kahwe Smith wrote: > Neil Conway wrote: > > I think a more sensible proposal could be made for some sort of optional > > "compatibility mode", as has been discussed many times in the past: > > different NULL handling could theoretically be part of an Oracle

Re: [HACKERS] Bitmap index status

On Wed, 18 Oct 2006, Heikki Linnakangas wrote: > Hi, > > I don't want to harass you :), but what's the status with the bitmap > index code? Is there something I can do to help? > Hi Heikki, The streaming is implemented, as are range queries. I need to bring it up to HEAD and back-patch to bizgre

Re: [HACKERS] Multiple postmaster + RPM + locale issues

Devrim GUNDUZ wrote: > However, I think we need to install locale files of each major > releases to different directory. No, you should rename the locale files, like psql-8.1.po. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--

Re: [HACKERS] [GENERAL] UDF and cache

And PLEASE do not post something to 3 lists; it's a lot of extra traffic for no reason. Moving to -hackers. On Wed, Oct 18, 2006 at 05:15:13PM -0400, jungmin shin wrote: > Hello all, > > I read a paper, which is Query optimization in the presence of Foreign > Functions. > And the paper , there

[HACKERS] Multiple postmaster + RPM + locale issues

Hi, I have almost finished working on multiple rpm + postmaster issue today. The spec file and patches in pgsqlrpms cvs work almost as expected and does some preliminary work about multiple postmaster installation issue (we can build the rpms and they are installed correctly). I have a question

Re: [HACKERS] UDF and cache

On Wed, Oct 18, 2006 at 05:15:13PM -0400, jungmin shin wrote: > Hello all, > > I read a paper, which is Query optimization in the presence of Foreign > Functions. > And the paper , there is a paragraph like below. > > In order to reduce the number of invocations, caching the results of > invoca

[HACKERS] UDF and cache

Hello all,   I read a paper,  which is Query optimization in the presence of Foreign Functions. And the paper , there is a paragraph like below.   In order to reduce the number of invocations, caching  the results of invocation was suggested in Postgres.   I'd like to know in detail about how postg

Re: [HACKERS] Performance/Security question on caching function OIDs for a connection

Weslee Bilodeau <[EMAIL PROTECTED]> writes: > On the input and output functions for the new type, I lookup the > encrypt/decrypt functions using - > FuncnameGetCandidates( list_make1( makeString( "decrypt" ) ) > Running through the list and getting the functions OID, then calling > with OidFu

[HACKERS] Performance/Security question on caching function OIDs for a connection

I'm working on my custom encryption types (as outlined in another thread) and was curious of one potential performance hit. On the input and output functions for the new type, I lookup the encrypt/decrypt functions using - FuncnameGetCandidates( list_make1( makeString( "decrypt" ) ) Runn

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

> > > Should work fine on Windows. fileno() is deprecated however, with > > > the following comment: > > > C:\Program Files\Microsoft Visual Studio > > > 8\VC\INCLUDE\stdio.h(688) : see > > > declaration of 'fileno' > > > Message: 'The POSIX name for this item is deprecated. > >

Re: [HACKERS] Mirror problems for download

> > I haven't noticed any torrent files for postgreSQL releases > - maybe we > > can look into setting this up to share the load, > particularly around > > release times. > > We used to release torrents but stopped because they weren't > all that popular. Search the archives for details. Not

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

"George Pavlov" <[EMAIL PROTECTED]> writes: >> It'd be interesting to verify whether it's the same on >> George's machine though. > Let me know how to test this. Identify the PID of one of your active backends (from "ps" or by looking in pg_stat_activity), and then run strace -p backend-

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

> the behavior. It'd be interesting to verify whether it's the same on > George's machine though. Let me know how to test this. (Please do a "for dummies" version -- I am not sure I can figure it out from the thread even though someone else might be able to.) ---(end of

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

I wrote: > I checked around with some kernel/glibc gurus in Red Hat, and the > consensus seemed to be that we'd be better off to bypass fprintf() and > just send message strings to stderr using write() --- ie, instead of > elog.c doing > fprintf(stderr, "%s", buf.data); > do >

Re: [HACKERS] pg_internal.init is hazardous to your health

On Wed, 2006-10-18 at 13:24 -0400, Tom Lane wrote: > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > RelationCacheInitFileInvalidate() is also called on each > > FinishPreparedTransaction(). > > Surely not... I take that to mean there's nothing special about prepared transactions and invalidating t

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

Tom Lane wrote: > "Magnus Hagander" <[EMAIL PROTECTED]> writes: > > Should work fine on Windows. fileno() is deprecated however, with the > > following comment: > > C:\Program Files\Microsoft Visual Studio > > 8\VC\INCLUDE\stdio.h(688) : see > > declaration of 'fileno' > > Message:

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, 2006-10-18 at 14:28 +0200, Andreas Joseph Krogh wrote: > On Wednesday 18 October 2006 14:15, Csaba Nagy wrote: > > > The following query returns NULL in PG: > > > SELECT NULL || 'fisk'; > > > > > > But in Oracle, it returns 'fisk': > > > SELECT NULL || 'fisk' FROM DUAL; > > > > > > The latt

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, Oct 18, 2006 at 11:36:44AM -0700, Jeff Davis wrote: > > What's being suggested simply violates common sense. Basically: > > > > if (a = b) then (a||c = b||c) > > > > If a is 'x' and b is 'x' and c is NULL, the above statement doesn't hold > in PostgreSQL. Heh, well, c is supposed to be

Re: [HACKERS] Bug?

Moving to -sql. On Wed, Oct 18, 2006 at 06:53:46PM +0530, Indira Muthuswamy wrote: > Hai, > > I have encountered a problem with PostgreSQL.I have created a table > 'tab1' with a column 'a' with serial type.I entered 20 records into the > table.So the query > select max(a) from tab1; > returned 2

Re: [HACKERS] bug or feature, || -operator and NULLs

Yes, well, we english speakers get to deal with the monstrosity that is 'www'. :) In any case, I believe coalesce is in the standard, and even if it's not, Oracle is the only database I know of that doesn't use it. If you're that unhappy with coalesce and ||, you can always create functions that

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, 2006-10-18 at 15:57 +0200, Martijn van Oosterhout wrote: > On Wed, Oct 18, 2006 at 03:44:05PM +0200, Andreas Joseph Krogh wrote: > > > When in doubt, consult the standard ... Oracle's treatment of NULL is > > > known to violate the standard, IIRC. Your measure of correctness seems > > > to

Re: [HACKERS] Mirror problems for download

On Wed, Oct 18, 2006 at 09:25:01PM +0930, Shane Ambler wrote: > I haven't noticed any torrent files for postgreSQL releases - maybe we > can look into setting this up to share the load, particularly around > release times. We used to release torrents but stopped because they weren't all that pop

Re: [HACKERS] analyzing debugging sentences.

On Wed, Oct 18, 2006 at 02:11:53PM -0400, jungmin shin wrote: > Hello, > > I set on for following items in postgresql.conf > > debug_print_parse > debug_print_rewritten > debug_print_plan > debug_print_pretty > > now, I can see something in PGAdmin query tool when I execute a query. > can I get

Re: [HACKERS] Getting the type Oid in a CREATE TYPE output function

Jim C. Nasby wrote: > On Tue, Oct 17, 2006 at 04:34:35PM +0300, Marko Kreen wrote: >>> I'm not sure if anyone else needs something like it, but it allows us to >>> transparently encrypt data directly in the tables. Minimum application >>> changes ('select enc_key' at connection) - the main requirem

Re: [HACKERS] Getting the type Oid in a CREATE TYPE output function

Marko Kreen wrote: > On 10/16/06, Weslee Bilodeau <[EMAIL PROTECTED]> wrote: >> Marko Kreen wrote: >> > The PGP functions happen to do it already - pgp_key_id(). >> >> Actually, Tom helped me realize I made a mistake, which I'm following >> his suggestion. Not tying keys to OIDs which change when b

Re: [HACKERS] analyzing debugging sentences.

jungmin shin wrote: Hello, I set on for following items in postgresql.conf debug_print_parse debug_print_rewritten debug_print_plan debug_print_pretty now, I can see something in PGAdmin query tool when I execute a query. can I get some idea how I can read comprehend the output? Plea

[HACKERS] analyzing debugging sentences.

Hello,   I set on for following items in postgresql.conf   debug_print_parse debug_print_rewritten debug_print_plan debug_print_pretty   now, I can see something in PGAdmin query tool when I execute a query. can I get some idea how I can read comprehend the output?   -- Executing query: select 0.4

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

"Magnus Hagander" <[EMAIL PROTECTED]> writes: > Should work fine on Windows. fileno() is deprecated however, with the > following comment: > C:\Program Files\Microsoft Visual Studio > 8\VC\INCLUDE\stdio.h(688) : see > declaration of 'fileno' > Message: 'The POSIX name for this item

Re: [HACKERS] Getting the type Oid in a CREATE TYPE output function

On Tue, Oct 17, 2006 at 04:34:35PM +0300, Marko Kreen wrote: > >I'm not sure if anyone else needs something like it, but it allows us to > >transparently encrypt data directly in the tables. Minimum application > >changes ('select enc_key' at connection) - the main requirement when > >working on le

Re: [HACKERS] pg_internal.init is hazardous to your health

"Simon Riggs" <[EMAIL PROTECTED]> writes: > RelationCacheInitFileInvalidate() is also called on each > FinishPreparedTransaction(). Surely not... regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your frie

Re: [HACKERS] Additional stats for Relations

Also how many times a relation has been vacuumed (which puts all the other numbers in more perspective... good catch Simon). And I think number of pages that could not be added to the FSM would also be extremely valuable. On Wed, Oct 18, 2006 at 11:27:39AM +0530, NikhilS wrote: > Hi, > > So: > he

Re: [HACKERS] Lock partitions

Tom Lane wrote: Mark Wong <[EMAIL PROTECTED]> writes: Tom Lane wrote: Hmm, what sort of errors are we talking about? ERROR: too many LWLocks taken That really shouldn't happen ... are you sure you did a full recompile after changing NUM_LOCK_PARTITIONS? Actually ... wait a moment. The d

Re: [HACKERS] Lock partitions

Mark Wong <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Hmm, what sort of errors are we talking about? > ERROR: too many LWLocks taken That really shouldn't happen ... are you sure you did a full recompile after changing NUM_LOCK_PARTITIONS? Actually ... wait a moment. The default value of

Re: [HACKERS] 8.1.5 is out

Teodor Sigaev <[EMAIL PROTECTED]> writes: > 1) Release notice mentions wronng > E.1.1. Migration to version 8.1.4 > ^ should be 8.1.5 Yup, noticed that the day after :-( > 2) It's very pity that ours Win32 fixes isn't in 8.1.5 :( That was intentional, at l

Re: [HACKERS] pg_internal.init is hazardous to your health

On Wed, 2006-10-18 at 12:49 +1000, Gavin Sherry wrote: > > We don't actually need to *update* the file, per se, we only need to > > remove it if no longer valid --- the next incoming backend will rebuild > > it. I could see fixing this by making WAL recovery run around and zap > > all the .init f

Re: [HACKERS] Lock partitions

Tom Lane wrote: Mark Wong <[EMAIL PROTECTED]> writes: The number of transaction errors increased when I increased the NUM_LOCK_PARTITIONS, which I think is the reason it failed to run when I set it to 16. Hmm, what sort of errors are we talking about? I wonder if you've exposed a bug. Chang

Re: [HACKERS] Lock partitions

Mark Wong <[EMAIL PROTECTED]> writes: > The number of transaction errors increased when I increased the > NUM_LOCK_PARTITIONS, which I think is the reason it failed to run when I > set it to 16. Hmm, what sort of errors are we talking about? I wonder if you've exposed a bug. Changing NUM_LOCK_

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wednesday 18 October 2006 14:44, Mario Weilguni wrote: > Am Mittwoch, 18. Oktober 2006 13:52 schrieb Andreas Joseph Krogh: > > This has been been discussed before, but Oracle behaves differently, and > > IMHO in a more correct way. > > > > The following query returns NULL in PG: > > SELECT NULL

Re: [HACKERS] Bitmap index status

On 10/18/06 2:41 AM, "Heikki Linnakangas" <[EMAIL PROTECTED]> wrote: > Hi, > > I don't want to harass you :), but what's the status with the bitmap > index code? Is there something I can do to help? Not at all. We will send you the new patch soon. Your comments are most appreciated. Thanks, Ji

Re: [HACKERS] 8.1.5 is out

Is this fix going to make it into 8.2? 8.0, 8.1 and 8.2. It commited in _STABLE branches -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(end of broadcast)-

Re: [HACKERS] 8.1.5 is out

On Wednesday 18 October 2006 11:15, Oleg Bartunov wrote: > On Wed, 18 Oct 2006, Teodor Sigaev wrote: > > 1) Release notice mentions wronng > > (http://www.postgresql.org/docs/8.1/interactive/release.html#RELEASE-8-1- > >5): E.1.1. Migration to version 8.1.4 > > ^ sho

Re: [HACKERS] Lock partitions

Tom Lane wrote: Bruce Momjian <[EMAIL PROTECTED]> writes: I see this in the CVS commits for 8.2. Did we determine the proper number of lock partitions? Should it be based on the number of buffers or concurrent sessions allowed? No. NUM_LOCK_PARTITIONS needs to be a compile-time constant for

Re: [HACKERS] bug or feature, || -operator and NULLs

Am Mittwoch, 18. Oktober 2006 15:07 schrieb Andreas Joseph Krogh: > Why do these discussions always end in academic arguments over whats more > logical then not? Because that is ultimately the reason why SQL behaves the way it does. I'm sure we could all come up with a long list of behaviors tha

Re: [HACKERS] bug or feature, || -operator and NULLs

> The following query returns NULL in PG: > SELECT NULL || 'fisk'; > > But in Oracle, it returns 'fisk': > SELECT NULL || 'fisk' FROM DUAL; > > The latter seems more logical... Why would it be more logical ? NULL means "value not known". Concatenate "value not known" with 'fisk' -> what's the

Re: [HACKERS] 8.1.5 is out

On Wed, 18 Oct 2006, Teodor Sigaev wrote: 1) Release notice mentions wronng (http://www.postgresql.org/docs/8.1/interactive/release.html#RELEASE-8-1-5): E.1.1. Migration to version 8.1.4 ^ should be 8.1.5 2) It's very pity that ours Win32 fixes isn't in 8.

Re: [HACKERS] bug or feature, || -operator and NULLs

even more exciting in this context would be to add user controllable NULL sorting behaviour. afaik this is in sql:2003. ORDER BY .. [ NULLS (FIRST|LAST) ] ? Wait a bit :), I'm waiting for separate 8.2 branch. -- Teodor Sigaev E-mail: [EMAIL PROTECTED]

[HACKERS] 8.1.5 is out

1) Release notice mentions wronng (http://www.postgresql.org/docs/8.1/interactive/release.html#RELEASE-8-1-5): E.1.1. Migration to version 8.1.4 ^ should be 8.1.5 2) It's very pity that ours Win32 fixes isn't in 8.1.5 :( tarball:2006-10-13 02:05:40

Re: [HACKERS] pg_internal.init is hazardous to your health

On Tue, 2006-10-17 at 22:29 -0400, Tom Lane wrote: > Dirk Lutzebaeck and I just spent a tense couple of hours trying to > figure out why a large database Down Under wasn't coming up after being > reloaded from a base backup plus PITR recovery. The symptoms were that > the recovery went fine, but b

Re: [HACKERS] bug or feature, || -operator and NULLs

Neil Conway wrote: I think a more sensible proposal could be made for some sort of optional "compatibility mode", as has been discussed many times in the past: different NULL handling could theoretically be part of an Oracle SQL dialect. even more exciting in this context would be to add user

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, 2006-10-18 at 15:44 +0200, Andreas Joseph Krogh wrote: > I'm not advocating that NULL should have a string-vaule of anything, just > that > the ||-operator shuld treat NULL as "dont bother with it and proceed > concatenation". Not only is the current behavior more logical (IMHO) and bac

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, 2006-10-18 at 16:15, Mario Weilguni wrote: > Yes it's hard for me, maybe because I am no native english speaker. Considering the pure latin origin of the word, that's a funny argument :-) BTW, I pronounce it as an Italian would (that would be the closest to it's origins): "koh-ah-less-ch

Re: [HACKERS] bug or feature, || -operator and NULLs

Yes it's hard for me, maybe because I am no native english speaker. -Ursprüngliche Nachricht- Von: Andrew Dunstan [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 18. Oktober 2006 16:11 An: Lukas Kahwe Smith Cc: Mario Weilguni; pgsql-hackers@postgresql.org Betreff: Re: [HACKERS] bug or feat

Re: [HACKERS] bug or feature, || -operator and NULLs

Lukas Kahwe Smith wrote: Mario Weilguni wrote: Nice, but I still prefer nvl. Coalesce is hard to pronounce, and even harder to type. amen .. coalesce was invented by a sadistic twit (something which people have also called me .. so it goes). Perhaps people are trying to pronounce it wrongly

Re: [HACKERS] bug or feature, || -operator and NULLs

Mario Weilguni wrote: Nice, but I still prefer nvl. Coalesce is hard to pronounce, and even harder to type. amen .. coalesce was invented by a sadistic twit (something which people have also called me .. so it goes). regards, Lukas ---(end of broadcast)-

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, Oct 18, 2006 at 03:44:05PM +0200, Andreas Joseph Krogh wrote: > > When in doubt, consult the standard ... Oracle's treatment of NULL is > > known to violate the standard, IIRC. Your measure of correctness seems > > to be "appears to me more logical", but ours is "complies with the > > stand

Re: [HACKERS] bug or feature, || -operator and NULLs

Andreas Joseph Krogh wrote: When in doubt, consult the standard ... Oracle's treatment of NULL is known to violate the standard, IIRC. Your measure of correctness seems to be "appears to me more logical", but ours is "complies with the standard". I know PG violates the standard in other pl

Re: [HACKERS] bug or feature, || -operator and NULLs

Nice, but I still prefer nvl. Coalesce is hard to pronounce, and even harder to type. -Ursprüngliche Nachricht- Von: Andreas Joseph Krogh [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 18. Oktober 2006 15:48 An: pgsql-hackers@postgresql.org Cc: Mario Weilguni Betreff: Re: [HACKERS] bug or

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wednesday 18 October 2006 15:15, Mario Weilguni wrote: > >If you want this behaviour you will have to explicitly handle it with > > COALESCE(). > > >regards, > >Lukas > > True. But there's a point where oracle is really better here, they named > "coalesce" "nvl" => a lot easier to type ;-) They

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wednesday 18 October 2006 15:13, Andrew Dunstan wrote: > Andreas Joseph Krogh wrote: > > This has been been discussed before, but Oracle behaves differently, and > > IMHO in a more correct way. > > > > The following query returns NULL in PG: > > SELECT NULL || 'fisk'; > > > > But in Oracle, it r

Re: [HACKERS] bug or feature, || -operator and NULLs

> >If you want this behaviour you will have to explicitly handle it with COALESCE(). > >regards, >Lukas True. But there's a point where oracle is really better here, they named "coalesce" "nvl" => a lot easier to type ;-) ---(end of broadcast)--- TI

Re: [HACKERS] Bug?

Indira Muthuswamy wrote: Hai, I have encountered a problem with PostgreSQL.I have created a table 'tab1' with a column 'a' with serial type.I entered 20 records into the table.So the query select max(a) from tab1; returned 20.When I tried the same query after the command truncate table

[HACKERS] Bug?

Hai,    I have encountered a problem with PostgreSQL.I have created a table 'tab1' with a column 'a' with serial type.I entered 20 records into the  table.So the query   select max(a) from tab1; returned 20.When I tried the same query after the command  truncate table tab1; I found that the output

Re: [HACKERS] bug or feature, || -operator and NULLs

> Why do these discussions always end in academic arguments over whats more > logical then not? Because you asked the (rhetorical from your POV) question 'isn't this more logical ?' > From a *user's* point of view I really would like it to > treat the NULL operand of || as '', and obviously ma

Re: [HACKERS] bug or feature, || -operator and NULLs

Andreas Joseph Krogh wrote: This has been been discussed before, but Oracle behaves differently, and IMHO in a more correct way. The following query returns NULL in PG: SELECT NULL || 'fisk'; But in Oracle, it returns 'fisk': SELECT NULL || 'fisk' FROM DUAL; The latter seems more logical...

Re: [HACKERS] bug or feature, || -operator and NULLs

Andreas Joseph Krogh wrote: > Why do these discussions always end in academic arguments over whats more > logical then not? From a *user's* point of view I really would like it to > treat the NULL operand of || as '', and obviously many other (at least > Oracle) users tend to agree with me on t

Re: [HACKERS] bug or feature, || -operator and NULLs

Andreas Joseph Krogh wrote: If aggregates ignore NULL one could argue that so shuld the ||-operator? I agree that this behaviour may seem pedantic, but changing this is only going to lead to a huge wtf? factor. The baviour for NULL in aggregates is pretty well documented and known. Even MySQ

Re: [HACKERS] Mirror problems for download

Magnus Hagander wrote: Michael Paesold wrote: I just wanted to download the postgresql-8.0.9 tarball. The page I got was this: Choose a download mirror Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz We could not query the database or no mirrors could be found! Download PostgreSQL from the

Re: [HACKERS] Mirror problems for download

> Not being subscribed to any more appropriate list, I post > this here on hackers. > > I just wanted to download the postgresql-8.0.9 tarball. The > page I got was this: > > Choose a download mirror > Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz > We could not query the database or no m

Re: [HACKERS] Mirror problems for download

Shane Ambler wrote: Michael Paesold wrote: Not being subscribed to any more appropriate list, I post this here on hackers. I just wanted to download the postgresql-8.0.9 tarball. The page I got was this: Choose a download mirror Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz We could n

Re: [HACKERS] bug or feature, || -operator and NULLs

Am Mittwoch, 18. Oktober 2006 13:52 schrieb Andreas Joseph Krogh: > This has been been discussed before, but Oracle behaves differently, and > IMHO in a more correct way. > > The following query returns NULL in PG: > SELECT NULL || 'fisk'; > > But in Oracle, it returns 'fisk': > SELECT NULL || 'fis

Re: [HACKERS] +1400 is a valid time zone offset

On Wed, Oct 18, 2006 at 02:52:35PM +0530, Abhijit Menon-Sen wrote: > In 1995, Kiribati decided to move the international date line, so that > all of the constituent islands lie on the same side. As a consequence, > the Easternmost islands are now at GMT+1400. > > (There's some controvery about whe

Re: [HACKERS] bug or feature, || -operator and NULLs

Martijn van Oosterhout wrote: By following your suggestion we would get the following oddity: SELECT NULL = '', NULL || 'fisk' = '' || 'fisk'; We would return NULL for the first and true for the second. Surely that's not logical? The problem is really that Oracle does not differntiate proper

Re: [HACKERS] bug or feature, || -operator and NULLs

> How many times do you *really* want to get the "not known" answer here > instead > of 'fisk'? To put it another way: When will it be *wrong* to return 'fisk'? All the time. If I would want the answer 'fisk', I would store '' instead of NULL... your problem is that Oracle treats NULL as '' (emp

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wed, Oct 18, 2006 at 02:28:50PM +0200, Andreas Joseph Krogh wrote: > On Wednesday 18 October 2006 14:15, Csaba Nagy wrote: > > > The following query returns NULL in PG: > > > SELECT NULL || 'fisk'; > > > > > > But in Oracle, it returns 'fisk': > > > SELECT NULL || 'fisk' FROM DUAL; > > > > > > T

Re: [HACKERS] bug or feature, || -operator and NULLs

On Wednesday 18 October 2006 14:15, Csaba Nagy wrote: > > The following query returns NULL in PG: > > SELECT NULL || 'fisk'; > > > > But in Oracle, it returns 'fisk': > > SELECT NULL || 'fisk' FROM DUAL; > > > > The latter seems more logical... > > Why would it be more logical ? How many times do

Re: [HACKERS] Asynchronous I/O Support

On Wed, Oct 18, 2006 at 08:04:29PM +1300, Mark Kirkwood wrote: > >"bgwriter doing aysncronous I/O for the dirty buffers that it is > >supposed to sync" > >Another decent use-case? Good idea, but async i/o is generally poorly supported. > Is it worth considering using readv(2) instead? Err, read

[HACKERS] bug or feature, || -operator and NULLs

This has been been discussed before, but Oracle behaves differently, and IMHO in a more correct way. The following query returns NULL in PG: SELECT NULL || 'fisk'; But in Oracle, it returns 'fisk': SELECT NULL || 'fisk' FROM DUAL; The latter seems more logical... -- Andreas Joseph Krogh <[EMA

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

> >> Hmm. If the messages are less than PIPE_BUF bytes long > (4096 bytes > >> on > >> Linux) then the writes are supposed to be atomic. > > > Some of them involve long messages (>4K), but there are > many that do > > not (like the ones I had posted at the start of this thread). > > I checke

Re: [HACKERS] Mirror problems for download

Michael Paesold wrote: Not being subscribed to any more appropriate list, I post this here on hackers. I just wanted to download the postgresql-8.0.9 tarball. The page I got was this: Choose a download mirror Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz We could not query the database

Re: [HACKERS] Syntax bug? Group by?

Dnia 17-10-2006 o godz. 23:21 Tom Lane napisał(a): > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > Mark Woodward wrote: > >> My question, is it a syntactic technicality that PostgreSQL asks for a > >> "group by," or a bug in the parser? > > > AFAIK what you want is not per sql spec. > > It wou

[HACKERS] Bitmap index status

Hi, I don't want to harass you :), but what's the status with the bitmap index code? Is there something I can do to help? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0,

[HACKERS] +1400 is a valid time zone offset

In 1995, Kiribati decided to move the international date line, so that all of the constituent islands lie on the same side. As a consequence, the Easternmost islands are now at GMT+1400. (There's some controvery about whether they had the right to move the IDL, but they have the right to decide wh

[HACKERS] Mirror problems for download

Not being subscribed to any more appropriate list, I post this here on hackers. I just wanted to download the postgresql-8.0.9 tarball. The page I got was this: Choose a download mirror Downloading: /source/v8.0.9/postgresql-8.0.9.tar.gz We could not query the database or no mirrors could be

Re: [HACKERS] 8.1.4 verified on Intel Mac OS 10.4.8

Douglas Toltzman wrote: The subject line says it all. I just completed a build, test, and install of PostgreSQL 8.1.4 on an Intel Mac with OS 10.4.8. Every single step executed flawlessly, and all 98 tests passed, running the regression tests. Just for info - there is an automated build far

Re: [HACKERS] [GENERAL] query log corrupted-looking entries

Tom Lane wrote: > I checked around with some kernel/glibc gurus in Red Hat, and the > consensus seemed to be that we'd be better off to bypass fprintf() and > just send message strings to stderr using write() --- ie, instead of > elog.c doing > > fprintf(stderr, "%s", buf.data); > > d

Re: [HACKERS] Asynchronous I/O Support

NikhilS wrote: Hi, "bgwriter doing aysncronous I/O for the dirty buffers that it is supposed to sync" Another decent use-case? Regards, Nikhils EnterpriseDB http://www.enterprisedb.com On 10/15/06, *Luke Lonergan* <[EMAIL PROTECTED] > wrote: Martijn, O