On Sun, Jan 29, 2006 at 10:20:47PM -0500, Neil Conway wrote:
> On Sun, 2006-01-29 at 17:03 -0800, David Fetter wrote:
> > Another followup, this time with the comment done right.
>
> + /* Disallow the forbidden_delimiter strings */
> + if (strcspn(cstate->delim, BADCHARS) != 1)
> +
On Thu, Jan 26, 2006 at 07:17:57PM +, ATTILA GATI wrote:
> create table test(id serial, txt varchar);
> create table mon(n int);
> create rule monitor as on insert to test do
> insert into mon values (NEW.id);
> insert into test (txt) values ('xxx');
>
> What I expect is to get the latest id w
On Sun, 29 Jan 2006, Bernhard Rosenkraenzer wrote:
Bug reference: 2220
Description:PostgreSQL-JDBC 8.1-404 fails to compile with ecj
Details:
PostgreSQL-JDBC 8.1-404 fails to compile (ecj bytecode compiler w/ gij 4.1
JDK):
This is because the driver dynamically decides what ve
On Sun, 2006-01-29 at 17:03 -0800, David Fetter wrote:
> Another followup, this time with the comment done right.
+ /* Disallow the forbidden_delimiter strings */
+ if (strcspn(cstate->delim, BADCHARS) != 1)
+ elog(ERROR, "COPY delimiter cannot be %#02x",
+
The following bug has been logged online:
Bug reference:
Logged by: Jim B
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: XP pro
Description:Can not reinstall due to account errors
Details:
Having uninstalled postgres 8.0.3, I neede
The following bug has been logged online:
Bug reference: 2220
Logged by: Bernhard Rosenkraenzer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Linux (Ark Linux 2006.1-pre)
Description:PostgreSQL-JDBC 8.1-404 fails to compile with ecj
Deta
Brian Hirt <[EMAIL PROTECTED]> writes:
> Yes, what you describe are exactly the circumstances that are
> required for our query to fail. Once again, thanks for the great
> help and quick fix. Do you think this fix will make 8.1.3?
It's already in CVS ...
regards, tom
On Sun, Jan 29, 2006 at 04:41:43PM -0800, David Fetter wrote:
> On Sun, Jan 29, 2006 at 09:50:08PM +, David Fetter wrote:
> >
> > The following bug has been logged online:
> >
> > Bug reference: 2221
> > Logged by: David Fetter
> > Email address: [EMAIL PROTECTED]
> > Postg
Tom,
Yes, what you describe are exactly the circumstances that are
required for our query to fail. Once again, thanks for the great
help and quick fix. Do you think this fix will make 8.1.3?
Best Regards,
Brian Hirt
On Jan 29, 2006, at 9:31 AM, Tom Lane wrote:
Brian Hirt <[EMAIL PROT
On Sun, Jan 29, 2006 at 09:50:08PM +, David Fetter wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2221
> Logged by: David Fetter
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: all
> Operating system: all
> Description:Bad delimit
The following bug has been logged online:
Bug reference: 2221
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: all
Operating system: all
Description:Bad delimiters allowed in COPY ... TO
Details:
This came up while I was testing my pg_dum
"Nicholas" <[EMAIL PROTECTED]> writes:
> Description:Variables selected in VIEWs under different names break
> queries using those views
This is a poor description, the problem actually seems to be related to
using sub-SELECTs in bitmap index scan conditions. Patch is here if you
need it
Brian Hirt <[EMAIL PROTECTED]> writes:
> I've run across a rather nasty bug in 8.1.2. It seems when the
> planer uses an index_scan within a GroupAggregate for a multi column
> index you can get incorrect results.
Patch is here if you need it before 8.1.3:
http://archives.postgresql.org/pgsql
Brian Hirt <[EMAIL PROTECTED]> writes:
> I've run across a rather nasty bug in 8.1.2. It seems when the
> planer uses an index_scan within a GroupAggregate for a multi column
> index you can get incorrect results.
Good catch. Looks to me like it only happens if two or more leading
index colu
14 matches
Mail list logo
