2.4 postgres database issues

[Keith Bellairs]

After a clean build (make clean; make), I cannot replicate the issues with a
fresh database. The problems persist for a pg database created in 2.3.17 a
few builds ago.  Given that 2.4 comes out clean, I think these are not a
bug.

On Tue, Dec 21, 2010 at 1:14 PM, John Ralls <jralls at ceridwen.us> wrote:

>
> On Dec 21, 2010, at 9:59 AM, Keith Bellairs wrote:
>
> > Since these are not replicated, I'll start with a make clean before I do
> anything else.
> >
> > On Tue, Dec 21, 2010 at 11:58 AM, John Ralls <jralls at ceridwen.us> wrote:
> >
> > On Dec 21, 2010, at 7:23 AM, Keith Bellairs wrote:
> >
> > > using a new gnucash db created with r19971 in postgres a few  odd
> things
> > > happen.
> > >
> > > 1. On reopening the db the following notices appear in the output in
> the
> > > command prompt window. Are these tables being receated every time?
> > >
> > > NOTICE:  CREATE TABLE will create implicit sequence
> "recurrences_id_seq1"
> > > for serial column "recurrences.id"
> > > NOTICE:  CREATE TABLE will create implicit sequence
> > > "taxtable_entries_id_seq1" for serial column "taxtable_entries.id"
> > > NOTICE:  CREATE TABLE will create implicit sequence "slots_id_seq1" for
> > > serial column "slots.id"
> > > NOTICE:  CREATE TABLE will create implicit sequence
> "budget_amounts_id_seq1"
> > > for serial column "budget_amounts.id"
> > >
> > > These notices appear each time that the existing pg db is opened on
> starting
> > > gnc.
> > >
> > > 2. The first action that would update the db such as entry of a new
> > > transaction generates an error message:
> > > Unable to save database
> > > in a popup. If I quit at that point the new transaction is lost. If I
> do
> > > other stuff it looks like subsequent saves work and the trans is
> recorded.
> > >
> > > 3. The lock on the postgres db is never cleared, so that I have to
> agree to
> > > override the lock each time the db is opened. This was a known bug that
> may
> > > have regressed.
> > >
> > > No time to run debug data out this AM. And maybe these are already know
> > > issues?
> > >
> >
> > I'm not able to replicate any of these. Please file a bug and we can
> troubleshoot it there.
> >
>
> Please remember to copy the list on replies.
>
> Make sure that you also really do start with a fresh database; use "Save
> as" to create a new one from whatever source you like (including the old
> database).
>
> Regards,
> John Ralls
>
>
>