Patch committed. Thanks.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of
On Tue, 15 Mar 2005, Oliver Siegmar wrote:
> Here's a demonstration of the bug:
>
> CREATE FUNCTION testfunction()
> RETURNS void
> AS '
> BEGIN
> CREATE TEMP TABLE testtable (field int4) ON COMMIT DROP;
>
> INSERT INTO testtable (field) VALUES (1);
>
> -- DROP TABLE te
On Fri, 18 Mar 2005, Oliver Siegmar wrote:
> On Friday 18 March 2005 14:29, Stephan Szabo wrote:
> > Given the error message, this seems to be the whole plpgsql caches query
> > plans but we don't invalidate those plans when there are schema changes.
>
> I already tried to execute the 'CREATE TEM
Uh, have you read the FAQ item about plpgsql and temporary tables?
---
Oliver Siegmar wrote:
> Hello,
>
> I've probably found a temp table bug in PostgreSQL (tested with 7.4.7 and
> 8.0.1 on Linux x86).
>
>
> Here's a de
Daniel van Eeden wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1549
> Logged by: Daniel van Eeden
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: Debian GNU/Linux for SPARC (sarge)
> Description:initdb doesn
Bruce Momjian writes:
> Daniel van Eeden wrote:
>> creating template1 database in /opt/postgresql/data/base/1 ... FATAL:
>> semctl(10977333, 16, SETVAL, 536) failed: Invalid argument
> That is a problem with semaphores in your kernel. Have you modified
> your postgresql.conf from the default?
On 2005-03-14, Tom Lane <[EMAIL PROTECTED]> wrote:
> The 8.0 planner is intentionally sensitive to the current actual
> physical sizes of tables. It sounds like you've managed to get it to
> plan something on the assumption that the tables are tiny and keep
> using that plan after they aren't tiny
Roy Badami wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1518
> Logged by: Roy Badami
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: Solaris 9
> Description:Conversions to (undocumented) SQL year-month and
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> It turns out that the scenario above is trivial to hit in 8.0 using
> referential constraints; RI triggers cache their plans, and on 8.0 the RI
> query is planned as a seqscan if the tables are freshly created. (On 7.4
> the plan is an index scan, th
Roy Badami wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1517
> Logged by: Roy Badami
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: Solaris 9
> Description:SQL interval syntax is accepted by the parser, bu
Bruce Momjian writes:
> Well, that certainly belongs in the 'bizarre' category. It should not
> accept that syntax. It should require the 'month' or 'minute' to be in
> single quotes.
No, it shouldn't; read the SQL spec. AFAICS the syntax
select interval '1' month
is perfectly spec-com
11 matches
Mail list logo
