"Paul van der Zwan" <[EMAIL PROTECTED]> writes:
> Only systems with large pagesizes support ISM, so always defining
> #define PG_SHMAT_FLAGS SHM_SHARE_MMU
> in src/backend/port/sysv_shmem.c will cause all calls to shmat to fail with
> EINVAL on systems that do not support large p
The following bug has been logged online:
Bug reference: 2411
Logged by: Nick Gould
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1-1
Operating system: Linux SuSe-10
Description:psql will not run, exits can't find libssl.o.4
Details:
This may not be suppo
The following bug has been logged online:
Bug reference: 2406
Logged by: Paul van der Zwan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Solaris
Description:Not all systems support SHM_SHARE_MMU
Details:
Only systems with large pagesiz
""Peter Brant"" <[EMAIL PROTECTED]> wrote
>
> I'm afraid we're in the same category as everyone else with no good way
> to reproduce the bug, but is there anything else we could do if this
> happens again?
>
There is a "Win32 semaphore patch" in the patch list, but we are lack of
evidence to prov
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Actually implementing this is left as a task for someone who feels like
>> hacking on the datetime code ... I don't particularly ...
> I think this is a perfect project for Summer of Code.
That's a thought. Another task in the same
Tom Lane wrote:
> BTW, I looked at the problem a little bit and concluded that it wouldn't
> be so invasive to fix as all that. The weak spot at the moment is that
> parse_coerce() passes typmod -1 instead of the specified typmod to the
> datatype's input routine when converting an unknown-type
Bruce Momjian writes:
> Tom Lane wrote:
>> We don't currently support that style of specifying interval constants,
>> and you shouldn't hold your breath expecting it to happen --- it will
>> require a whole bunch of abuse of the currently data-type-independent
>> processing of literal constants.
Tom Lane wrote:
> Bruce Momjian writes:
> > That is definately a bug:
> > test=> SELECT INTERVAL '100' YEAR;
>
> We don't currently support that style of specifying interval constants,
> and you shouldn't hold your breath expecting it to happen --- it will
> require a whole bunch of abuse of
Bruce Momjian writes:
> That is definately a bug:
> test=> SELECT INTERVAL '100' YEAR;
We don't currently support that style of specifying interval constants,
and you shouldn't hold your breath expecting it to happen --- it will
require a whole bunch of abuse of the currently data-type-inde
On Apr 21 05:29, Balázs Klein wrote:
> Description:case insensitive match for unicode doesn't work
Case conversion of multibyte characters related bugs has been resolved
in cvs tip and will be available for 8.2.
> I raised this issue on pgsql.general -
> http://groups.google.com/group/pg
On Sat, Apr 22, 2006 at 20:34:03 +,
"Harry E. Clarke" <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2403
> Logged by: Harry E. Clarke
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: Suse Li
Harry E. Clarke wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2403
> Logged by: Harry E. Clarke
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: Suse Linux 10.0
> Description:Date arithemtic using INTERVAL in
The following bug has been logged online:
Bug reference: 2403
Logged by: Harry E. Clarke
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Suse Linux 10.0
Description:Date arithemtic using INTERVAL in UPDATE command does
not work
Details:
The following bug has been logged online:
Bug reference: 2402
Logged by: Balázs Klein
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Gentoo Linux
Description:case insensitive match for unicode doesn't work
Details:
case conversion and ca
while the postgresql-8.1.3-1 installation,for the section "install as a service"
if i selected or checked it and press "next"...the msg do not hv "log on as a service"right.prompt out (figure1.jpg).if i press "No" ,critical error msg appear (figure2.jpg).else the msg (
figure3.jpg) di
Aren't you using EMS Postgresql Manager?
I kept getting this message for any non-standard UTF8 character that I
wanted to insert or import.
I wrote to them and they said EMS PgManager does not yet support
unicode.
Balázs
---(end of broadcast)---
TI
The following bug has been logged online:
Bug reference: 2405
Logged by: RIMBAUD
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux RH3
Description:how to know if a cursor is open
Details:
In pgsql 7.2 , we can close a cursor before c
17 matches
Mail list logo
