stella escribió:
> we experience a problem after upgrating to 8.3.4 from 8.2.5 as we use 'ORDER
> BY' clause. The old version sorted char starting with null characters first
> for example ' anything' would be before 'anything'. Saw there are some new
> options NULLS FIRST/LAST, but they are not
The following bug has been logged online:
Bug reference: 4526
Logged by: stella
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: linux
Description:Problem with sorting order by clause and null
values(space) in the beginning og a string
Det
I apologize in advance for not testing on 8.3.5, but that would be very
difficult for me.
here is where it works in 8.3.1:
protocalte=> select version() ;
version
Pos
On Wed, Nov 12, 2008 at 06:45:27PM +, chris wood wrote:
> I apologize in advance for not testing on 8.3.5, but that would be very
> difficult for me.
> I e-mailed this same problem from [EMAIL PROTECTED] and it got
> blocked
http://www.postgresql.org/docs/current/interactive/release-8-3-2.ht
Faithful record-keeping this ML(pgsql-bug).
Fixed the bug in both Windows and Ubuntu platforms.
It is uuid-ossp version 1.6.2.
Thanks!
Regards,
Hiroshi Saito
- Original Message -
From: "Ismael Ciordia, Openbravo" <[EMAIL PROTECTED]>
Subject: RE: [BUGS] BUG #4167: When generating UUID
The following bug has been logged online:
Bug reference: 4525
Logged by: chris wood
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Debian
Description:substring with this pattern works in 8.3.1; does not
work in 8.3.4
Details:
I apologiz
Ooops, It will be helpful to a user.
Therefore, it transmits here.:-)
Thanks!!
-- copy --
Hi Hiroshi-san,
if you want you can include the function we have used to test the problem,
pasted below.
Regards,
Ismael
**
CREATE OR REPLACE FUNCTION test_uuidgen(countmax INTEGER) RETUR
"Moussard" <[EMAIL PROTECTED]> writes:
> Using the "TO_CHAR" function, the ".US" format doesn't display the correct
> value for the microseconds part of a timestamp value.
If you're using floating-point timestamps, this isn't a bug --- it's
just inevitable platform-specific roundoff error. The pa
The following bug has been logged online:
Bug reference: 4523
Logged by: Moussard
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: i686-redhat-linux-gnu
Description:TO_CHAR function : the ".US" format returns incorrect
value
Details:
Usin
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Yeah, the reason this hasn't ever been seen is that normally we don't
> have permissions to signal init.
... and that the only consequence of the failed kill() would be that the
launcher doesn't get the signal to rebalance costs after a worker
launch, w
Heikki Linnakangas escribió:
> Zou Yong wrote:
>> I was running postgres on a Linux with busybox. The autovacuum feature is
>> turned on. I noticed that the autovacuum worker sent SIGUSR1 to pid 1 which
>> is the init process and caused the system halt.
>
> Hmm. The postgres user shouldn't have pe
Zou Yong wrote:
Bug reference: 4522
Logged by: Zou Yong
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Linux 2.6.24
Description:autovacuum working send SIGUSR1 to the wrong pid
Details:
I was running postgres on a Linux with busybox. T
The following bug has been logged online:
Bug reference: 4522
Logged by: Zou Yong
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Linux 2.6.24
Description:autovacuum working send SIGUSR1 to the wrong pid
Details:
I was running postgres o
Dey, Sutapa wrote:
Hi
All,
I
am trying to build/enable plperl support for postgres.
1.
The system info is :
#
uname -a
HP-UX
unknown B.11.23 U 9000/800 1178464650 unlimited-user license
2.
The steps I followed:
a)
In
postgres user’s .profile file I
14 matches
Mail list logo
