L.S.
After an upgrade to v8.4 one of our clients is experiencing heaps of problems,
they get errors like "ERROR: SPI_connect failed: SPI_ERROR_CONNECT".
I refer to this earlier post, it looks a lot like it:
http://archives.postgresql.org/pgsql-general/2009-07/msg00388.php
We too had no
Frank van Vugt writes:
> Any clues as to how to gather additional information that might bring us
> closer to a solution is appreciated also.
A stack trace from the point of the error would probably tell us a great
deal. Maybe you could attach to a backend with gdb, set a breakpoint
at the fail
Hi Tom,
Op maandag 13 juli 2009, schreef Tom Lane:
> Frank van Vugt writes:
> > Any clues as to how to gather additional information that might bring us
> > closer to a solution is appreciated also.
>
> A stack trace from the point of the error would probably tell us a great
> deal. Maybe you co
Frank van Vugt writes:
> Just fyi, a breakpoint at SPI_connect with condition
> _SPI_curid != _SPI_connected
Right, that's what to look for.
> produced the following backtrace:
> Program received signal SIGUSR2, User defined signal 2.
> 0x2b539af2b5f5 in recv () from /lib64/libc.so.6
On Fri, Jul 10, 2009 at 12:31:05PM -0400, Alvaro Herrera wrote:
- Dan Boeriu wrote:
- > Could you please tell me how you installed it? What exact version did you
download? Was it source or yum/rpm?
- > I tried both with source compiling with the flags for oops-uuid and still
didn't get the functi
David Kerr wrote:
> ---
> With regards to Service Request # 10497898141:
>
> Thank you for the response. Since the PostgreSQL project determined
> uuid off by default, the SLES RPMs have been left at the default.
> Recompiling with the settings to turn on uuid is how to enable uuid,
> but recomp
(Please reply to the list, not just to me)
I'm not sure about this so far. Re the specific issue you mention of
conversion between cp1250 and latin-2 (ISO-8859-2) the Unicode tables
at:
http://unicode.org/Public/MAPPINGS/ISO8859/8859-2.TXT
appear to agree - there's no PER MILLE in ISO-8859-2.
Craig Ringer writes:
> Your problem, though, is that if you connect to a LATIN2 database with a
> WIN1250 client and INSERT a string containing the per-mille glyph, Pg
> accepts it and it should not. If it does, indeed, accept it, then I
> agree that's a bug.
The table in win12502mic() in latin2_
The following bug has been logged online:
Bug reference: 4918
Logged by: Frank Spies
Email address: frank.sp...@biotronik.com
PostgreSQL version: 8.4
Operating system: Linux
Description:Weird input syntax for intervals
Details:
It feels totally weird that the two qu
"Frank Spies" writes:
> It feels totally weird that the two queries
> 1) select interval '13 month'
> 2) select interval '13' month
> do not have the same result: result for 1) is "1 year 1 mon", result for 2
> is "1 mon". Is this correct behaviour?
$ psql
psql (8.4.0)
Type "help" for help.
regr
On Monday 13 July 2009 19:17:49 David Kerr wrote:
> We're using SLES 11, and uuid-ossp isn't delivered in the
> postgresql-contrib package, we opened a case with Novell and this was their
> reply:
> [some nonsense]
I'm sorry to say that SUSE just isn't a good source if you want to do serious
Post
On Tue, Jul 14, 2009 at 01:18:55AM +0300, Peter Eisentraut wrote:
- On Monday 13 July 2009 19:17:49 David Kerr wrote:
- > We're using SLES 11, and uuid-ossp isn't delivered in the
- > postgresql-contrib package, we opened a case with Novell and this was their
- > reply:
- > [some nonsense]
-
- I'm
12 matches
Mail list logo
