Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Oh, the query actually gives an assertion failure on an
> assertion-enabled build, so this is clearly a bug:
> TRAP: FailedAssertion("!(attnum > 0 && attnum <=
> list_length(rte->joinaliasvars))", File: "parse_relation.c", Line: 1697)
Okay, I look
On Thu, Apr 03, 2008 at 12:24:17AM +0200, Peter Eisentraut wrote:
> Jeff Dwyer wrote:
> > This works fine:
> > select 1 where current_date between '1900-3-3' and '1900-2-2';
> > This doesn't:
> > select 1 where current_date between coalesce(null,current_date) and
> > coalesce(null, '1900-1-2');
>
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I still haven't seen the actual bug description come by here, and the
pgsql-bugs archive hasn't got it either.
(apparently some mails on that thread are missing ...)
That's what I meant. Heikki is quoting himself f
Tom Lane wrote:
That's what I meant. Heikki is quoting himself from a message that
hasn't appeared anywhere public, and he must have had at least one
message from the OP that hasn't appeared either. So the rest of us
are still mostly in the dark about the problem.
I got this one, which app
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I still haven't seen the actual bug description come by here, and the
>> pgsql-bugs archive hasn't got it either.
> (apparently some mails on that thread are missing ...)
That's what I meant. Heikki is quoting himself from a message
Tom Lane wrote:
> I still haven't seen the actual bug description come by here, and the
> pgsql-bugs archive hasn't got it either.
http://archives.postgresql.org/pgsql-bugs/2008-03/msg00351.php
and continues in April here
http://archives.postgresql.org/pgsql-bugs/2008-04/msg00031.php
(apparent
The following bug has been logged online:
Bug reference: 4088
Logged by: Carlos Alexadnre
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: W2K
Description:Server doesn't listen
Details:
The server doesn't accept connections: the connection
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Actually rows are supposed to be limited
>> to ~1600 columns, anyway, because of HeapTupleHeader limitations.
> The trick is that that limitation doesn't apply to the intermediate
> virtual tuples we move around in the executor.
Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
On second thought, expanding AttrNumber to int32, wholesale, might not
be a good idea,
No, it wouldn't. For one thing it'd be a protocol break --- column
numbers are int16 ---
I wasn't planning to change that.
and for another
Pavel Golub <[EMAIL PROTECTED]> writes:
> Just curious, what was the reason?
http://archives.postgresql.org/pgsql-hackers/2008-04/msg00044.php
http://archives.postgresql.org/pgsql-committers/2008-04/msg7.php
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsq
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> On second thought, expanding AttrNumber to int32, wholesale, might not
> be a good idea,
No, it wouldn't. For one thing it'd be a protocol break --- column
numbers are int16 --- and for another, we'd have terrible performance
problems with such wi
OK, worksforme. I guess I still find it odd, but I much prefer
explicitness & robustness to small values of 'work'.
Thanks for the prompt response.
-Jeff
On Apr 2, 2008, at 7:15 PM, Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Jeff Dwyer wrote:
This seems like a bug to me.
"jitendra" <[EMAIL PROTECTED]> wrote:
> I'm jitendra from delhi(India),I've a problem with table creation using
> pythonscript executed but there's nothing happened.
> the program written in python is...
You need to add conn.commit() here:
>cur.execute("create table ph2 (nm varchar,
Premysl Paska napsal(a):
The following bug has been logged online:
Bug reference: 4084
Logged by: Premysl Paska
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.15
Operating system: Linux
Description:Some DST timezones switche to summer time (one week)
later
The following bug has been logged online:
Bug reference: 4087
Logged by: jitendra
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: rhel 5
Description:table creation problem using python
Details:
hi,
I'm jitendra from delhi(India),I've a p
Hello, Tom.
Thank a lot Tom.
Just curious, what was the reason?
Regards
You wrote:
TL> "Pavel Golub" <[EMAIL PROTECTED]> writes:
>> Comparing 8.3.1 to 8.2.5 release INSERT of >1000 rows is very slow.
>> INSERT INTO numbers (numberint, numberstr) VALUES (1, 'One');
>> INSERT INTO numbers (numb
16 matches
Mail list logo
