Re: [ic] Issue with Postgres (current transaction is aborted), followup

[Ethan Rowe <suppressed>]

Stefan Hornburg wrote:

> On Thu, 2 Jun 2005 10:03:50 -0500
> Mike Heins <suppressed> wrote:
>
>  
>
> > Quoting Stefan Hornburg (Racke) (suppressed):
> >    
> >
> > > Hello,
> > >
> > > from my original message:
> > >
> > > --- SNIP ---
> > > Hello, list !
> > >
> > > RPO Vienna encounters a peculiar error with Interchange and Postgres.
> > > Suddenly, PostgreSQL doesn't accept any database modifications through
> > > Interchange for any catalogs running on this server. 
> > >
> > > Sometimes an error message can be found:
> > >
> > > iro /cgi-bin/iro/process Runtime error: DBD::Pg::st execute failed: ERROR:  current transaction is aborted, queries ignored until end of transaction block at /usr/local/interchange/lib/Vend/Table/DBI.pm line 1
> > > 446.
> > >      
> > >
> > > A restart "fixes" this problem.
> > >      
> > Restart of what? IC, or postgres?
> >    
>
> IC.
>
>  
>
> > > --- SNAP ---
> > >
> > > We don't need transactions, so 
> > >
> > > DatabaseDefault HAS_TRANSACTIONS 0
> > >
> > > can be used as workaround.
> > >
> > > However, I think IC has to address this issue in order to avoid
> > > serious and unexpected data loss.
> > >
> > >      
> > I have never heard of this problem before, but unless we get more
> > information surrounding the issue there will be no chance to fix
> > it.
> >    
>
> Forgot this link:
>
> http://mail.pm.org/pipermail/spug-list/2004-December/006143.html
>
>  
>
> > I have to some extent lost patience with Postgres and DBD::Pg, as
> > it seems to have constant little problems that change from version
> > to version of each.
> >    
>
> Hehe. I also feel that Postgres more cumbersome to deal with for
> web apps.
>  
It is regretable that your experience has brought about this conclusion; 
I've had exactly the opposite experience and find PostgreSQL vastly 
preferable to MySQL for pretty much anything.  It's like oil paints 
versus Crayola crayons.  Oil paints can be somewhat tempermental and 
frustrating, but with (extreme) patience yield excellent results.  
Crayons are nice and easy, and that's about it.  That said, the DBD::Pg 
maintainers do unfortunate things from time to time, and I've certainly 
seen problems with Interchange and PostgreSQL that are unpleasant to solve.

In any case, did your PostgreSQL logs tell you where the first error 
within the transaction was occurring?  The error must have occurred in 
the master Interchange process, right?  (which doesn't make any sense to 
me).

--
Ethan Rowe
End Point Corporation
suppressed
_______________________________________________
interchange-users mailing list
suppressed
http://www.icdevgroup.org/mailman/listinfo/interchange-users