On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe <[email protected]>wrote:
> On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh <[email protected]> > wrote: > > I took your cue, and have formulated this solution for 8.3.1 : > > Is there a good reason you're running against a db version with known > bugs instead of 8.3.5? Seriously, it's an easy upgrade and running a > version missing over a year of updates is not a best practice. > That's just a development instance that I have kept for long; actual issue was on EDB 8.3.0.12, which the customer is using. As noted in the PS of previous mail, the solution that worked for PG 8.3.1 didn't work on EDB 8.3.0.12, so had to come up with a different code for that! Best regards, -- gurjeet[[email protected] singh.gurj...@{ gmail | hotmail | indiatimes | yahoo }.com EnterpriseDB http://www.enterprisedb.com Mail sent from my BlackLaptop device
