Gianfranco Pesce ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Date represetation bug. Some dates are incorrectly selected
Long Description
Some dates are incorrectly selected from pgsql and from the C preprocessor. The same
POSTGRESQL BUG REPORT TEMPLATE
Your name : Dmitry G. Mastrukov
Your email address : [EMAIL PR
POSTGRESQL BUG REPORT TEMPLATE
Your name : Dmitry G. Mastrukov
Your email address : [EMAIL PR
from: john foderaro, [EMAIL PROTECTED]
platform: x86 running Redhat 6.2 Linux from rpm
postgresql-server-6.5.3-6
postgresql version: 6.5.3 (my guess based on rpm name).
problem: count() return the wrong result given a very simple join:
sample: we create a table of 3 elements an
Good day.
System Configuration
-
Architecture: Intel Pentium
Operating System: FreeBSD 3.5-STABLE
PostgreSQL version: PostgreSQL-7.0.3
Compiler used: gcc 2.7.2.3
Description of problem
--
I have some problem with creating new type in pgsql.
Dmitry G . Mastrukov writes:
> Configure crashes on build from separate build directory with
> mkdir: Cannot make directory 'src/backend/port': No such file or
> directory
Do you get *any* directories created under the build tree? Can you go
into config/prep_buildtree and change /bin/sh to /bin
John Foderaro <[EMAIL PROTECTED]> writes:
> postgresql version: 6.5.3 (my guess based on rpm name).
Fixed long since ... update ...
regards, tom lane
Not sure how to handle this. I have never heard of Heimdal, and I am
afraid these changes will adversely affect other Kerberos users. My
inclination is to not make any changes and wait to see if another user
reports a problem.
[ Charset KOI8-R unsupported, converting... ]
> ===
Dmitry G . Mastrukov writes:
> 1. Configure cannot properly determine Heimdal (0.3d - 0.3e) libs.
> Heimdal has no libk5crypto, all its functions is in libkrb5. Configure
> crashes.
> 2. a) Heimdal has no enc_part2 member in krb5_ticket
> b) Heimdal has no text member in krb5_error
These thi
[EMAIL PROTECTED] writes:
> test=> create table pippo (d date);
> CREATE
> test=> insert into pippo values ('22/05/1977');
> INSERT 629024 1
> test=> insert into pippo values ('28/05/1978');
> INSERT 629025 1
> test=> select * from pippo;
> d
>
> 21/05/1977
> 27/05/1978
> (2 row
"And. Andruikhanov" <[EMAIL PROTECTED]> writes:
> create type unsl4(input=unsl4_in, output=unsl4_out, internallength=4,
> externallength=variable);
This will not work at all, since you did not specify PASSEDBYVALUE
but your functions assume the type is pass-by-value. An explicit
ALIGNMENT=int4
On Mon, Feb 26, 2001 at 10:34:05PM -0500, Tom Lane wrote:
> Robert Hentosh ([EMAIL PROTECTED]) writes:
> > Postgresql was compiled with ./configure --enable-syslog after
> > modifying "#define BLCKSZ 16384" in src/include/config.h.in
>
> Hm. I wonder if that is triggering the problem, or if it's
Robert Hentosh <[EMAIL PROTECTED]> writes:
> Where should I have looked to find out that I was exhausting my
> resources? I would like to size the system correctly when I test my
> application.
One would like to think that the postmaster log would've showed
resource-related error messages. Howe
13 matches
Mail list logo