On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe <span dir="ltr">&lt;<a href="mailto:scott.marlowe@gmail.com">scott.marlowe@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh &lt;<a href="mailto:singh.gurjeet@gmail.com">singh.gurjeet@gmail.com</a>&gt; wrote:<br>
&gt; I took your cue, and have formulated this solution for 8.3.1 :<br>
<br>
</div>Is there a good reason you&#39;re running against a db version with known<br>
bugs instead of 8.3.5? &nbsp;Seriously, it&#39;s an easy upgrade and running a<br>
version missing over a year of updates is not a best practice.<br>
</blockquote></div><br>That&#39;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&#39;t work on EDB 8.3.0.12, so had to come up with a different code for that!<br>
<br>Best regards, <br>-- <br>gurjeet[.singh]@EnterpriseDB.com<br>singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com<br><br>EnterpriseDB &nbsp; &nbsp; &nbsp;<a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br>
<br>Mail sent from my BlackLaptop device<br>