The following bug has been logged online:
Bug reference: 5485
Logged by: Jakub Bogacz
Email address: jakubbog...@o2.pl
PostgreSQL version: 8.4.1, 9.0.0
Operating system: Windows 7
Description:Microsoft VC++ exception during postgres instalation
Details:
Hi,
Since I
On 31/05/2010 4:01 PM, Jakub Bogacz wrote:
The following bug has been logged online:
Bug reference: 5485
Logged by: Jakub Bogacz
Email address: jakubbog...@o2.pl
PostgreSQL version: 8.4.1, 9.0.0
Operating system: Windows 7
Description:Microsoft VC++ exception during
As a workaround you can run the installer with a CLI option
'--install_runtimes 0' which will skip the VC++ runtimes installation,
However if your system doesn;t have those runtimes installation will
fail subsequently in the later stages.
From the the installation logs found in %TEMP%, you can
Robert Haas wrote:
> On Sat, May 29, 2010 at 5:00 PM, Bruce Momjian wrote:
> > I have updated the patch, attached, to clarify that this returns text
> > arrays, and that you can force it to always return one row using
> > COALESCE() and a '|' pattern (the later suggested by Daniele Varrazzo).
>
>
Daniele Varrazzo wrote:
> On Sun, May 30, 2010 at 4:45 AM, Robert Haas wrote:
> > On Sat, May 29, 2010 at 5:00 PM, Bruce Momjian wrote:
> >> I have updated the patch, attached, to clarify that this returns text
> >> arrays, and that you can force it to always return one row using
> >> COALESCE()
John Regehr wrote:
> Hi Tom,
>
> > If you can show me rewrites of all the basic arithmetic operations that
> > detect overflow in full compliance with the C standard, and are
> > readable, portable, and efficient, I'm all ears.
>
> These are the best ones that I know of:
>
> https://www.secureco
Bruce Momjian writes:
> Consider improving overflow detection
> *
> http://archives.postgresql.org/message-id/4bc66a57.2030...@cs.utah.edu
I did look at those at the time, and saw absolutely no reason to prefer
them over what we do now.
regards, tom lane
Tom Lane wrote:
> Bruce Momjian writes:
> > Consider improving overflow detection
> >*
> > http://archives.postgresql.org/message-id/4bc66a57.2030...@cs.utah.edu
>
> I did look at those at the time, and saw absolutely no reason to prefer
> them over what we do now.
OK, removed from
Pavel Stehule wrote:
> 2010/4/15 Tom Lane :
> > Pavel Stehule writes:
> >> I think, so RETURNS TABLE can be modified for returning typmode
> >> without significant problems - this function is called in table
> >> context and I don't see any problematic use case.
> >
> > RETURNS TABLE is just a sho
The following bug has been logged online:
Bug reference: 5487
Logged by: Takahiro Itagaki
Email address: itagaki.takah...@oss.ntt.co.jp
PostgreSQL version: 9.0beta1
Operating system: Linux
Description:dblink failed with 63 bytes connection names
Details:
Contib/dbli
"Takahiro Itagaki" wrote:
> Bug reference: 5487
> Logged by: Takahiro Itagaki
> Email address: itagaki.takah...@oss.ntt.co.jp
> Description:dblink failed with 63 bytes connection names
> Details:
>
> Contib/dblink module seems to have a bug in handling
> connection n
2010/5/31 Bruce Momjian :
> Pavel Stehule wrote:
>> 2010/4/15 Tom Lane :
>> > Pavel Stehule writes:
>> >> I think, so RETURNS TABLE can be modified for returning typmode
>> >> without significant problems - this function is called in table
>> >> context and I don't see any problematic use case.
>>
12 matches
Mail list logo
