Re: [PATCHES] temporal version of generate_series()

2008-05-01 Thread H . Harada
2008/5/1 Pavel Stehule [EMAIL PROTECTED]: Hello why you don't use polymorphic types? Ah, good idea. I didn't think we could fix the third argument to interval but anyelement. For a temporal version, it's reasonable. Also, the name generate_time_series is better than before? Hitoshi Harada

Re: [PATCHES] plpgsql CASE statement - last version

2008-05-01 Thread Pavel Stehule
Hello 2008/5/1 Jaime Casanova [EMAIL PROTECTED]: On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello I found some bugs when I used base_lexer, so I returned back own lexer. It's only little bit longer, but simpler. you really compile this one? i get a complain

Re: [PATCHES] plpgsql CASE statement - last version

2008-05-01 Thread Jaime Casanova
On Thu, May 1, 2008 at 7:59 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello 2008/5/1 Jaime Casanova [EMAIL PROTECTED]: On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello I found some bugs when I used base_lexer, so I returned back own lexer. It's only little

Re: [PATCHES] plpgsql CASE statement - last version

2008-05-01 Thread Jaime Casanova
On Thu, May 1, 2008 at 8:11 AM, Jaime Casanova [EMAIL PROTECTED] wrote: On Thu, May 1, 2008 at 7:59 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello 2008/5/1 Jaime Casanova [EMAIL PROTECTED]: On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello I found

Re: [PATCHES] plpgsql CASE statement - last version

2008-05-01 Thread Jaime Casanova
On Thu, May 1, 2008 at 8:14 AM, Jaime Casanova [EMAIL PROTECTED] wrote: On Thu, May 1, 2008 at 8:11 AM, Jaime Casanova [EMAIL PROTECTED] wrote: On Thu, May 1, 2008 at 7:59 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello 2008/5/1 Jaime Casanova [EMAIL PROTECTED]: On Sat, Apr 5,

Re: [PATCHES] temporal version of generate_series()

2008-05-01 Thread H . Harada
2008/5/1 H. Harada [EMAIL PROTECTED]: 2008/5/1 Pavel Stehule [EMAIL PROTECTED]: Hello why you don't use polymorphic types? Ah, good idea. I didn't think we could fix the third argument to interval but anyelement. For a temporal version, it's reasonable. I was thinking about it

Re: [PATCHES] plpgsql CASE statement - last version

2008-05-01 Thread Jaime Casanova
On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule [EMAIL PROTECTED] wrote: Hello I found some bugs when I used base_lexer, so I returned back own lexer. It's only little bit longer, but simpler. you really compile this one? i get a complain because read_sql_construct is called with 8 arguments

Re: [PATCHES] temporal version of generate_series()

2008-05-01 Thread Pavel Stehule
2008/5/1 H. Harada [EMAIL PROTECTED]: 2008/5/1 H. Harada [EMAIL PROTECTED]: 2008/5/1 Pavel Stehule [EMAIL PROTECTED]: Hello why you don't use polymorphic types? Ah, good idea. I didn't think we could fix the third argument to interval but anyelement. For a temporal version, it's

Re: [PATCHES] Removing NONSEG mode

2008-05-01 Thread Tom Lane
Zdenek Kotala [EMAIL PROTECTED] writes: I attach patch which remove nonsegment mode support. It was discussed during last commit fest. Nonsegment mode is possible uses only on couple of FS (ZFS, XFS) and it is not safe on any OS because each OS support more filesystems. Applied with revisions

Re: [PATCHES] Fix \dT enum in psql

2008-05-01 Thread Andrew Dunstan
David Fetter wrote: Folks, In psql, \dT doesn't show the elements for enums. Please find patch vs. CVS TIP attached which fixes this per the following TODO item: http://archives.postgresql.org/pgsql-hackers/2008-01/msg00826.php I don't have a particular problem with this patch -

Re: [PATCHES] Fix \dT enum in psql

2008-05-01 Thread David Fetter
On Thu, May 01, 2008 at 10:53:00PM -0400, Andrew Dunstan wrote: David Fetter wrote: Folks, In psql, \dT doesn't show the elements for enums. Please find patch vs. CVS TIP attached which fixes this per the following TODO item:

[PATCHES] configure option for XLOG_BLCKSZ

2008-05-01 Thread Mark Wong
Hi all, I saw a that a patch was committed that exposed a configure switch for BLCKSZ. I was hoping that I could do that same for XLOG_BLCKSZ. I think I got the configure.in, sgml, pg_config_manual.h, and pg_config.h.in changes correct. Regards, Mark Index: configure

Re: [PATCHES] configure option for XLOG_BLCKSZ

2008-05-01 Thread Tom Lane
Mark Wong [EMAIL PROTECTED] writes: I saw a that a patch was committed that exposed a configure switch for BLCKSZ. I was hoping that I could do that same for XLOG_BLCKSZ. Well, we certainly *could*, but what's the use-case really? The case for varying BLCKSZ is marginal already, and I've seen