Fujii Masao wrote:
> Heikki Linnakangas wrote:
> >> I found the typo in
> >> http://www.postgresql.org/docs/8.3/static/datatype-enum.html .
> >>
> >>> The length of an enum value's textual label is limited by the NAMEDATALEN
> >>> setting compiled into PostgreSQL; in standard builds this means at m
Aleksej Saushev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4053
> Logged by: Aleksej Saushev
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3
> Operating system: NetBSD, but this does no matter
> Description:libpq documentation
Peter Eisentraut wrote:
> Tom Lane wrote:
> > plpgsql does not consider standard_conforming_strings --- it still uses
> > backslash escaping in its function bodies regardless. Since the
> > language itself is not standardized, I see no particular reason that
> > standard_conforming_strings should
Bill Thoen <[EMAIL PROTECTED]> writes:
> The table seems fine this time, and there was no segfaulting nonsense at
> any time. But the server log was a lot more active. Whe I loaded this
> data the first time and had that corruption prroblem, there was hardly
> anything posted to the log. However
Tom Lane wrote:
If you have the time and interest, it might be worth repeating the
whole setup sequence starting from initdb. I'm speculating that
installing PostGIS might have somehow left corruption in server memory
that later manifested as the visible problem.
Tom,
I'm not sure if I did
kannan wrote:
> The following bug has been logged online:
>
> Bug reference: 4259
> Logged by: kannan
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 2005
There is no version 2005 of PostgreSQL. Additionally, the query syntax
you have provided below looks like it'd onl
The following bug has been logged online:
Bug reference: 4259
Logged by: kannan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 2005
Operating system: Windows 2003 Server
Description:I don't understand this query
Details:
create table [dbo].[olapobjects] (
