I wrote:
> I guess we need a hack
> to treat empty outer join conditions specially.
Actually, it can happen with non-empty join conditions too, if the join
condition doesn't mention the outer side; for instance, using your
example
explain SELECT * from fooview fv1
LEFT OUTER JOIN fooview fv2 o
Tom Lane wrote:
> "Joost Karaaijeveld" <[EMAIL PROTECTED]> writes:
> > Printing a timestamp using '%t%' in Windows omits the timezone in the
> > logfile. In Linux the timezone is printed. Either make the two the same by
> > default or make it configurable so that the user can make them the same.
>
Hi,
On Tue, 2006-12-12 at 19:23 +0530, Danish Siddiqui wrote:
> Im not able to install postgresql-8.1.2 on CentOS 4.1
"How" it is not working? What is the error message?
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> Test suite (as simple as I can produce):
Mmm, sweet :-(. There is only one legal way to form the outer join, but
make_rels_by_joins() doesn't try it because have_relevant_joinclause()
says there is no relevant joinclause ... as indeed there is not, the
Danish Siddiqui wrote:
Im not able to install postgresql-8.1.2 on CentOS 4.1
What's the error you're getting?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner
Sorry, versions are 8.2 & 8.3. 8.1 works well
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 9: In versions be
Test suite (as simple as I can produce):
CREATE TABLE foo (a int, b int);
INSERT INTO foo VALUES (1,2);
INSERT INTO foo VALUES (2,3);
INSERT INTO foo VALUES (3,3);
CREATE VIEW fooview AS
SELECT
f1.a AS a_for_max_b
FROM
( SELECT MAX(foo.b) AS MaxB FROM foo ) f2
Im not able to install postgresql-8.1.2 on CentOS 4.1
#uname -a
Linux localhost.localdomain 2.6.9-11.EL #1 Wed Jun 8 16:59:52 CDT 2005
i686 i686 i386 GNU/Linux
Thanks
Danish
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL pr
Pavel Golub <[EMAIL PROTECTED]> writes:
> Documentation says:
> "User-defined type names cannot begin with the
> underscore character (_)
We've never actually enforced that AFAIK, so this might be considered a
documentation bug.
> CREATE TYPE _my AS (id int4, id2 int4);
>
> CREATE TABLE my_table(
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> The question that jumps at me is why are you using SPI inside a type's
> output function? You should really avoid doing that.
Offhand it seems like it should work, but the real problem is that there
are probably a ton of code paths besides SPI_getvalue
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> This bug seems to be introduced by this recent change to avoid memory
> leakage:
I see no crash in CVS tip --- I believe it's same bug fixed here:
2006-12-07 19:40 tgl
* src/backend/executor/: spi.c (REL8_2_STABLE), spi.c: Avoid double
The following bug has been logged online:
Bug reference: 2824
Logged by:
Email address: pgsql-bugs@postgresql.org
PostgreSQL version: 8.2
Operating system: Windows 2003 Server
Description:Problem with installation by Remote Desktop
Details:
Message with unexpected
J. Greg Davidson wrote:
> I have a user defined type implemented in C and SPI which has been
> crashing a lot. I found a small enough case to trace the whole thing
> with gdb and found that while connected to SPI I was doing a get_value
> on a type T implemented in C and SPI. SPI_getvalue led to
This bug seems to be introduced by this recent change to avoid memory
leakage:
Log Message:
---
Prevent intratransaction memory leak when a subtransaction is aborted
in the middle of executing a SPI query. This doesn't entirely fix the
problem of memory leakage in plpgsql exception han
The issue below was reported to us as a pgAdmin bug - it can be
recreated in psql on 8.2.0, and results in:
2006-12-12 09:06:50 LOG: server process (PID 4588) exited with exit
code -1073741819
2006-12-12 09:06:50 LOG: terminating any other active server processes
2006-12-12 09:06:50 WARNING:
Hello, pgsql-bugs.
Documentation says:
"User-defined type names cannot begin with the
underscore character (_) and can only be 62
characters long (or in general NAMEDATALEN - 2,
rather than the NAMEDATALEN - 1 characters
allowed for other names). Type names beginning
with underscore are reserved f
16 matches
Mail list logo
