[BUGS] helo

2010-02-22 Thread beulah prasanthi
Helo I am working on spring project with postgres 8.4 i wrote a function in postgrees which i am passing the argument email email[] array From front end we need to insesrt data into that emailarray .so i used java.arraylist.util while i am running i got the following error Please help me

[BUGS] TypeCast: util.list to array type

2010-02-22 Thread beulah prasanthi
Helo I am working on spring project with postgres 8.4 i wrote a function in postgrees which i am passing the argument email email[] array From front end we need to insesrt data into that emailarray .so i used java.arraylist.util while i am running i got the following error Please help me

[BUGS] typecast exception

2010-02-22 Thread beulah prasanthi
Helo I am working on spring project with postgres 8.4 i wrote a function in postgrees which i am passing the argument email email[] array From front end we need to insesrt data into that emailarray .so i used java.arraylist.util while i am running i got the following error Please help me

[BUGS] typecast exception

2010-02-22 Thread beulah prasanthi
-- Forwarded message -- From: Ravi nm.ravi2...@gmail.com Date: Mon, Feb 22, 2010 at 5:21 PM Subject: To: Prasanthi itsbeu...@gmail.com Method in Dao public void savePerson(Person person, ListAddress addresses, ListEmail emails, ListPhone numbers){ call.withProcedureName(

[BUGS] exception in plsql

2010-02-22 Thread beulah prasanthi
show details 5:21 PM (19 minutes ago) Method in Dao public void savePerson(Person person, ListAddress addresses, ListEmail emails, ListPhone numbers){ call.withProcedureName( person_save1); MapString, Object out = call.execute(new PGPerson(person),addresses,null,null); }

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Bruce Momjian
Was this ever addressed? --- Tom Lane wrote: Kevin Grittner kevin.gritt...@wicourts.gov writes: Tom Lane t...@sss.pgh.pa.us wrote: I'm not sure whether we'd want to provide a function within libpq for this, or just

Re: [BUGS] helo

2010-02-22 Thread Kevin Grittner
Kris Jurka bo...@ejurka.com wrote: You need to pass an instance of java.sql.Array, not a Collection or something else that is array like. Ah, right. After extracting an array from the java.util.ArrayList, it needs to be turned into a java.sql.Array using the Connection.createArrayOf method.

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Kevin Grittner
Bruce Momjian br...@momjian.us wrote: Was this ever addressed? It should probably be on the TODO list. I was going to try to do this along with other items which came out of generating an LSB conforming init script, but have been pulled in different directions for now. When I get the time

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Bruce Momjian
Kevin Grittner wrote: Bruce Momjian br...@momjian.us wrote: Was this ever addressed? It should probably be on the TODO list. I was going to try to do this along with other items which came out of generating an LSB conforming init script, but have been pulled in different directions

[BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Jonathan
The following bug has been logged online: Bug reference: 5339 Logged by: Jonathan Duke Leto Email address: jonat...@leto.net PostgreSQL version: master 0f50d482 Operating system: CentOS 5.4 (Linux kernel 2.6.18) Description:Version of Perl detected incorrectly

Re: [BUGS] BUG #5118: start-status-insert-fatal

2010-02-22 Thread Kevin Grittner
Bruce Momjian br...@momjian.us wrote: I think you should just edit the TODO wiki and list all the things we agree need fixing Will do. It may take me a while to chase down all the issues from the LSB script work. If I recall correctly, some of what I was looking at seems necessary for a

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 10:57, Jonathan jonat...@leto.net wrote: The following bug has been logged online: Bug reference:      5339 Logged by:          Jonathan Duke Leto Email address:      jonat...@leto.net PostgreSQL version: master 0f50d482 Operating system:   CentOS 5.4 (Linux kernel

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 12:44, Alex Hunsaker bada...@gmail.com wrote: On Mon, Feb 22, 2010 at 10:57, Jonathan jonat...@leto.net wrote: configure: using perl configure: WARNING: *** The installed version of Perl, /home/leto/bin/perl, is too old to use with PostgreSQL. *** Perl version 5.8 or

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alvaro Herrera
Alex Hunsaker escribió: On Mon, Feb 22, 2010 at 10:57, Jonathan jonat...@leto.net wrote: checking for perl... /home/leto/bin/perl configure: using perl configure: WARNING: *** The installed version of Perl, /home/leto/bin/perl, is too old to use with PostgreSQL. *** Perl version 5.8

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Tim Bunce
Using perl -e 'use 5.008010' would be a more reliable way for configure to test the perl version. Tim. On Mon, Feb 22, 2010 at 05:57:56PM +, Jonathan Duke Leto wrote: The following bug has been logged online: Bug reference: 5339 Logged by: Jonathan Duke Leto

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Tom Lane
Alex Hunsaker bada...@gmail.com writes: On Mon, Feb 22, 2010 at 10:57, Jonathan jonat...@leto.net wrote: This is perl 5, version 11, subversion 4 (v5.11.4-114-ga4cc961*) built for x86_64-linux Ugh. Can't they manage to keep that message reasonably consistent? ! perl_version_error=`$PERL

[BUGS] BUG #5340: Requirement of different syntax on different OS

2010-02-22 Thread pradeep
The following bug has been logged online: Bug reference: 5340 Logged by: pradeep Email address: patilpradeep...@yahoo.com PostgreSQL version: 1.10.1 Operating system: windows 7 Description:Requirement of different syntax on different OS Details: If I am using

Re: [BUGS] BUG #5340: Requirement of different syntax on different OS

2010-02-22 Thread Jaime Casanova
On Mon, Feb 22, 2010 at 2:51 PM, pradeep patilpradeep...@yahoo.com wrote: The following bug has been logged online: Bug reference:      5340 Logged by:          pradeep Email address:      patilpradeep...@yahoo.com PostgreSQL version: 1.10.1 Operating system:   windows 7 Description:      

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Jonathan Leto
Howdy, On Mon, Feb 22, 2010 at 12:07 PM, Tom Lane t...@sss.pgh.pa.us wrote: Alex Hunsaker bada...@gmail.com writes: On Mon, Feb 22, 2010 at 10:57, Jonathan jonat...@leto.net wrote: This is perl 5, version 11, subversion 4 (v5.11.4-114-ga4cc961*) built for x86_64-linux Ugh.  Can't they

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Tom Lane
Jonathan Leto jonat...@leto.net writes: On Mon, Feb 22, 2010 at 12:07 PM, Tom Lane t...@sss.pgh.pa.us wrote: This is perl 5, version 11, subversion 4 (v5.11.4-114-ga4cc961*) built for x86_64-linux Ugh.  Can't they manage to keep that message reasonably consistent? The form of the version

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 13:07, Tom Lane t...@sss.pgh.pa.us wrote: Alex Hunsaker bada...@gmail.com writes: !   perl_version_error=`$PERL -e 'use 5.00801;' 21` This is not a path towards an acceptable solution, as it effectively assumes what we are setting out to prove, namely that we have

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread David Fetter
On Mon, Feb 22, 2010 at 02:17:57PM -0700, Alex Hunsaker wrote: On Mon, Feb 22, 2010 at 13:07, Tom Lane t...@sss.pgh.pa.us wrote: Alex Hunsaker bada...@gmail.com writes: !   perl_version_error=`$PERL -e 'use 5.00801;' 21` This is not a path towards an acceptable solution, as it effectively

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Tom Lane
Alex Hunsaker bada...@gmail.com writes: How about something like the below? I still think that this is optimizing the wrong thing. We care about the clarity of the message the user sees, not about how short or clean the Perl code is. I'm inclined to stay with the same basic implementation and

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 14:17, Alex Hunsaker bada...@gmail.com wrote: On Mon, Feb 22, 2010 at 13:07, Tom Lane t...@sss.pgh.pa.us wrote: Alex Hunsaker bada...@gmail.com writes: !   perl_version_error=`$PERL -e 'use 5.00801;' 21` ... How about something like the below? Find attached one that

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 14:31, Tom Lane t...@sss.pgh.pa.us wrote: Alex Hunsaker bada...@gmail.com writes: How about something like the below? I still think that this is optimizing the wrong thing.  We care about the clarity of the message the user sees, not about how short or clean the Perl

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Jonathan Leto
Howdy, First, thanks to everyone for the quick responses to my bug report. The output format of perl -v has been reasonably consistent for well over a decade, eg (examples captured from various machines around my house)        This is perl, version 4.0        This is perl, v5.8.7 built for

Re: [BUGS] BUG #5103: pg_ctl -w (re)start fails with custom unix_socket_directory

2010-02-22 Thread Bruce Momjian
Michael Renner wrote: Alvaro Herrera wrote: Michael Renner wrote: Mentioning PGHOST in pg_ctl's manpage/documentation should make this entirely clear for people who aren't familiar with the extensive environment variables PostgreSQLs client library can use. [1] Yeah, this has

Re: [BUGS] to_char issue?

2010-02-22 Thread Bruce Momjian
Dave Page wrote: This was posted as a documentation comment: to_char(interval '0d 0h 12m 44s', 'DD HH MI SS'); with HH and HH12 will return 12 instead of 0. Testing on 8.4.1, it does seem to be the case that you get 00 12 12 44. Seems bogus to me, but am I and the OP missing something?

Re: [BUGS] to_char issue?

2010-02-22 Thread Bruce Momjian
Bruce Momjian wrote: Dave Page wrote: This was posted as a documentation comment: to_char(interval '0d 0h 12m 44s', 'DD HH MI SS'); with HH and HH12 will return 12 instead of 0. Testing on 8.4.1, it does seem to be the case that you get 00 12 12 44. Seems bogus to me, but am I and

[BUGS] BUG #5341: problema al iniciar pgadmin

2010-02-22 Thread Jaime Mendieta
The following bug has been logged online: Bug reference: 5341 Logged by: Jaime Mendieta Email address: mendie...@gmail.com PostgreSQL version: 8.4.2 Operating system: Windows Vista Description:problema al iniciar pgadmin Details: cuando termino de instalar postgres

Re: [BUGS] to_char issue?

2010-02-22 Thread Bruce Momjian
bruce wrote: Dave Page wrote: This was posted as a documentation comment: to_char(interval '0d 0h 12m 44s', 'DD HH MI SS'); with HH and HH12 will return 12 instead of 0. Testing on 8.4.1, it does seem to be the case that you get 00 12 12 44. Seems bogus to me, but am I and the OP

Re: [BUGS] BUG #5341: problema al iniciar pgadmin

2010-02-22 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Feb 23, 2010 at 01:42:30AM +, Jaime Mendieta wrote: The following bug has been logged online: Bug reference: 5341 [...] cuando termino de instalar postgres 8.4.2 me sale un cuadro que dice Problem running post-install step.

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Mon, Feb 22, 2010 at 14:31, Tom Lane t...@sss.pgh.pa.us wrote: I'm inclined to stay with the same basic implementation and just hack up the regexp some more to cope with 5.11's more verbose -v output. And here is a stab at that: $ echo This is perl, version 4.0 | sed -n 's/This is

Re: [BUGS] BUG #5339: Version of Perl detected incorrectly

2010-02-22 Thread Alex Hunsaker
On Tue, Feb 23, 2010 at 00:50, Alex Hunsaker bada...@gmail.com wrote: On Mon, Feb 22, 2010 at 14:31, Tom Lane t...@sss.pgh.pa.us wrote: I'm inclined to stay with the same basic implementation and just hack up the regexp some more to cope with 5.11's more verbose -v output. And here is a stab