Neil Conway <[EMAIL PROTECTED]> writes:
> Yeah, this seems bogus. It's not even clear to me why MAXDATELEN +
> MAXDATEFIELDS is used as the size of that buffer in the first place. I
> don't know the datetime code particularly well; perhaps someone who does
> can shed some light on this?
My rule
Mark Dilger wrote:
It appears that any string representation of an interval of length greater
than 76 is rejected. (76 = 51 + 25 = MAXDATELEN + MAXDATEFIELDS). This
appears to be a limitation enforced within function interval_in() in the
file src/backend/utils/adt/timestamp.c
Yeah, this seems bog
On Tue, May 17, 2005 at 05:05:03PM -0400, Gregory L Miller-Kramer wrote:
> On system One I enter the database ...
> psql exdb exdb
> select misspelled_excol from extable;
>
> and an error is displayed...
> ERROR: column 'misspelled_excol' does not exist
>
> On the "Other" system (Postgres 8.0) t
"Gregory L Miller-Kramer" <[EMAIL PROTECTED]> writes:
> Postgres8 does not return errors for some reason. If you look at the errors
> generated on dev or purposely cause an error in psql you will see what I
> mean. All errors are being dumped to /opt/pgsql/pgstartup.log.
This report is pretty uncl
On Wed, 11 May 2005, Pavel Krupets wrote:
> Bug reference: 1661
> PostgreSQL version: 8.0.2
> Description:JDBC DatabaseMetaData.getExportedKeys() returns invalid
> keys.
>
> If I ask getExportedKeys(null, "bc4jgen_test_04", "table_03") to return
> exported foreign keys it will retu
"Brian Hackett" <[EMAIL PROTECTED]> writes:
> From manual examination of the code, it looks like pg_restore will corrupt
> an internal data structure on certain abnormal inputs.
Yeah, I think you are right. Looks easy to fix though: we already are
building a flag array from the input, so just add
>From manual examination of the code, it looks like pg_restore will corrupt
an internal data structure on certain abnormal inputs.
File: postgresql-8.0.2/src/bin/pg_dummp/pg_backup_archiver.c
SortTocFromFile pulls dump IDs out of a file and uses them to sort the list
entries in field toc of archi
On Mon, May 16, 2005 at 02:16:34PM +0100, Gregory L Miller-Kramer wrote:
>
> Postgres8 does not return errors for some reason.
In what context?
> If you look at the errors generated on dev or purposely cause an
> error in psql you will see what I mean.
Please provide an example so we can see exa
Tom,
Try turning off SELinux enforcement, or better update the selinux
policy package and do a restorecon on all of /usr/bin. The earlier
I'll definitely give this a try.
Does this policy also apply to binaries compiled on the local machine?
When I compiled PG803 from source, then copied pg_dump
The following bug has been logged online:
Bug reference: 1672
Logged by: Gregory L Miller-Kramer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: CentOS 4.0
Description:Postgres 8.0 doesn't return errors.
Details:
To Whom it may concern:
10 matches
Mail list logo
