On Thu, Apr 7, 2011 at 5:50 AM, Craig Ringer
<craig@postnewspapers.com.au> wrote:
> On 06/04/11 18:51, tejas tank wrote:
>
>> What should I have to do.?????
>
> Read this:
> http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> and try again with a question that includes an example you can
> distribute to show others the problem, including any required data, as a
> single .sql file. Most likely, you will find the bug in your code while
> trying to boil it down to a self-contained test case.
>
>> Its urgent ....
>
> If it's urgent for you, pay a consultant to help you. There are plenty. See:
>
> http://www.postgresql.org/support/professional_support
>
> Alternately, please respect the time of the people here who're
> volunteering to help. Put together a question with enough information
> for someone to actually be able to help you. Remember that urgent for
> you doesn't make it urgent for anyone else.
>
> http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> --
> Craig Ringer
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
The current subject is alarming and it sure seems like it is not a
PostgreSQL bug hence it is potentially misleading, and the issue has
not been put to rest as the original author has gone silent and not
responding to the various offers to help on this matter. Maybe it's
time to reformat the subject if it okay.
Allan.