On Tue, Jan 6, 2009 at 2:24 AM, Gurjeet Singh <singh.gurjeet@xxxxxxxxx> wrote: > On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> > wrote: >> >> On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh <singh.gurjeet@xxxxxxxxx> >> 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! Ahh, ok. I was just worried you were ignoring updates. I don't know anything about the numbering scheme for EDB. What does 8.3.0.12 translate to in regular pgsql versions? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
