Greg
> > We now have a basic patch set that works and is basically stable (not > > recommended for production servers!).
We'vededicated a page at our web > > site and it hopefully has answers to most of your questions, and also > > has the
patchset for download. These are for 7.4.19 - the version > > included with RHEL 4.
http://www.ExtSQL.com/postgres_notes.php> > This is kind of interesting, but targeting 7.4.19 isn't going to
getyou > very far toward code anyone else will use. That release is 6 years old, > it's filled with unsolvable
limitations,it's basically at end of life. > The fact that it's bundled with RHEL4 and there are some legacy installs >
stillfloating around are the only reason it's not completely gone from > everyone's radar.> > In short, if you actually
careabout your data, you should be running a > newer version of the database regardless of what RHEL ships. And you >
shouldbe building patches against no earlier than 8.4 if you want > something that has any hope of being accepted into
mainstreamdevelopment. > Eventually the patch will need to apply to the 8.5 work in progress source > code tree before
it'seven a candidate to merge. You can probably get > away with developing against a more stable version like 8.4.1,
ifyou must > target something people can also deploy, but even that's not ideal and > will eventually turn into a code
mergehurdle.
Yes, thanks for the recommendation and I do agree. I think we
got started with 7.4.19 because we run RHEL4 and had a postgresql
installation in support of a Canit anti-SPAM system -- it gave us
something real to test against.
We were trying to decided what later release to target, looks
like we'll go for 8.4 and 8.5 as staff/work permits. Any feedback on
the syntax/output is welcome.
Best regards!
-- John
____________________________________________________________________
John Murtari Software Workshop Inc.
jmurtari@thebook.com "software that fits!" (TM)
(315) 944-0999 (x-211) http://www.SoftwareWorkshop.com/
