The following bug has been logged online:
Bug reference: 5022
Logged by: Tyler Burd
Email address: tb...@cudc.org
PostgreSQL version: 8.4
Operating system: Windows Server 2008
Description:unkown winsock error 10061
Details:
Upgraded from 8.3.4 to 8.4, and we started
On Fri, Aug 21, 2009 at 9:35 AM, Pramod wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5003
> Logged by: Pramod
> Email address: pramodchoudhar...@yahoo.com
> PostgreSQL version: 8.4.0-1
> Operating system: Windows XP
> Description: setup error
>
On Fri, Aug 28, 2009 at 1:38 PM, Kevin
Grittner wrote:
> Merlin Moncure wrote:
>
>> This leads to some very weird behaviors, for example 'coalesce(foo,
>> something)' and 'case when foo is null then something else foo end'
>> can give different answers.
>
> Quite apart from the issue you're pursui
Merlin Moncure wrote:
> This leads to some very weird behaviors, for example 'coalesce(foo,
> something)' and 'case when foo is null then something else foo end'
> can give different answers.
Quite apart from the issue you're pursuing, this is another example of
how the COALESCE predicate in P
On Wed, Aug 26, 2009 at 5:55 AM, Ishara wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5013
> Logged by: Ishara
> Email address: ishara...@gmail.com
> PostgreSQL version: 8.4
> Operating system: Solaris x86
> Description: Error in psqlodbc config
Merlin Moncure writes:
> Today I ran into a problem relating to $subject. plpgsql's handling
> of 'null' composite types is not consistent with what you get in sql:
Hm. It looks like plpgsql treats composite arguments as being "row"
instead of "record" variables, which has some possible efficie
Today I ran into a problem relating to $subject. plpgsql's handling
of 'null' composite types is not consistent with what you get in sql:
create table foo(a text, b text);
create table bar(id int, f foo);
insert into bar values (1, ('a', 'b'));
create or replace function f(_foo out foo) returns
The following bug has been logged online:
Bug reference: 5021
Logged by: Dan O'Hara
Email address: danarasoftw...@gmail.com
PostgreSQL version: 8.3.7
Operating system: win32
Description:ts_parse doesn't recognize email addresses with
underscores
Details:
In the foll
Magnus Hagander escribió:
> On Fri, Aug 28, 2009 at 05:03, Alvaro Herrera
> wrote:
> > It would be good, but currently that list comes from a database that
> > cannot handle external lists. Since that database also powers the
> > search engine, I am very afraid to touch it ... particularly since
On Fri, Aug 28, 2009 at 4:01 AM, Helena Biander wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5020
> Logged by: Helena Biander
> Email address: hebiguard-s...@yahoo.se
> PostgreSQL version: 8.4
> Operating system: WinXP
> Description: Stackbuild
The following bug has been logged online:
Bug reference: 5020
Logged by: Helena Biander
Email address: hebiguard-s...@yahoo.se
PostgreSQL version: 8.4
Operating system: WinXP
Description:Stackbuilder not functioning
Details:
When trying to run stackbuilder at instal
On Thu, Aug 27, 2009 at 19:41, Tom Lane wrote:
> Magnus Hagander writes:
>> 2009/8/27 Tom Lane :
>>> Magnus Hagander writes:
Fix applied - exports.txt had a tab in it, instead of spaces, to
separate the field from the number.
>>>
>>> Hmm, maybe it would be better to fix whatever sed scr
On Fri, Aug 28, 2009 at 05:03, Alvaro Herrera wrote:
> Robert Haas escribió:
>> 2009/8/27 Alvaro Herrera :
>> > Robert Haas escribió:
>> >
>> >> Para obtener ayuda en espan~ol, tal vez puede Ud. tratar
>> >> pgsql-es-ay...@postgresql.org. Creo que no tenemos una list de correo
>> >> en Portugue's.
13 matches
Mail list logo
