Karla Peralta <[EMAIL PROTECTED]> writes:
>> Show us a sequence of queries that causes these messages, and we'll
>> fix it ...
> The messages show ups in two queries
It hardly seems likely that such simple queries would trigger a failure
like this. I believe, for example, that you must be using
Tom Lane wrote:
> Karla Peralta <[EMAIL PROTECTED]> writes:
> >> A bug with symptoms similar to this was fixed in 7.0.3. Please
> >> try 7.0.3, and let us know if you still have problems.
>
> > Now I'm using postgresql-7.0.3-2 but I have the same problem.
>
> Oh well :-(
>
> > What else can i do
Karla Peralta <[EMAIL PROTECTED]> writes:
>> A bug with symptoms similar to this was fixed in 7.0.3. Please
>> try 7.0.3, and let us know if you still have problems.
> Now I'm using postgresql-7.0.3-2 but I have the same problem.
Oh well :-(
> What else can i do
Show us a sequence of que
Tom Lane wrote:
> Karla Peralta <[EMAIL PROTECTED]> writes:
> > PostgreSQL version :7.0.2-2
>
> > I startup my program in the client and sometimes a get this :
>
> > Notice: Begin already a transaction in progress
> > Notice: BlankPortalAssignName: portal myportal already exists
> > Notice:
Alan Turner <[EMAIL PROTECTED]> writes:
> test=# CREATE FUNCTION "f2" ( ) RETURNS magic AS '
> test'# DECLARE
> test'# x RECORD;
> test'# BEGIN
> test'# x.one := 1;
> test'# x.two := 2;
> test'# RETURN x;
> test'#
Hello
I believe have discovered a bug in PostgreSQL version 7.0.3. Here is a quick
bug report. I have tried to include any information which might be useful, but
if I have left anything out, please let me know, and I shall provide it. I
could possibly rebuild PostgreSQL with debugging symbols an
