This is a discussion on Re: cron: sh /usr/local/src/pgadmin3/pkg/src/build-tarball;sh /usr/local/src/pgadmin3/pkg/slackware/build-snapshot 91 within the pgsql Interfaces Pgadmin Hackers forums, part of the PostgreSQL category; --> > -----Original Message----- > From: Andreas Pflug [mailto gadmin@pse-consulting.de] > Sent: 24 February 2005 16:49 > To: Dave Page ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > -----Original Message----- > From: Andreas Pflug [mailto > Sent: 24 February 2005 16:49 > To: Dave Page > Cc: pgadmin-hackers@postgresql.org > Subject: Re: cron: sh > /usr/local/src/pgadmin3/pkg/src/build-tarball;sh > /usr/local/src/pgadmin3/pkg/slackware/build-snapshot 91 > > Dave Page wrote: > > > >>Dormant. If anybody wants to continue on that, I can give > some hints > >>what to do next. > > > > > > OK... Mark is doing a scheduler for another job at the moment, so it > > seems the ideal time to finish that one as well and save doing some > > design/research work twice. What needs doing? > > Major rework of data model. It's implemented using oids as > pk, because > it's so convenient inserting something and getting the key from the > insert. Must be rewritten to int4 columns and a sequence, otherwise > backup/restore isn't possible. Urgh. That doesn't sound like something you'd do! > AFAIR basic sql/shell executes are working, code for win32 service > manager is basically there, but no linux daemonization. OK. > Dialogs to create/edit a schedule needed. I'm thinking of something > really comfortable, which will need quite some ui work. OK. > Mark should contact me directly for explanations what my > thoughts where > when spitting out that code. Many ideas might not become clear from > looking at those CFC (comment free code ;-) It'll probably be me doing most of the work, but comparing notes with him as we go :-) Cheers, Dave. ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |