Problem solved:
I reinstall postgres from sources, works.
pasman
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
This is not a bug. Try to ask on pgsql-general.
2011/9/2, Maggie Brooks :
>
> The following bug has been logged online:
>
> Bug reference: 6196
> Logged by: Maggie Brooks
> Email address: maggie.bro...@claraview.com
> PostgreSQL version: 9.0.4
> Operating system: Windows XP
>
Workaround is:
git config core.crlf=false
--
pasman
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hi.
This is not postgresql bug. Try pgadmin-support list.
Btw psql < script is too complicated?
2011/8/2, michael :
>
> The following bug has been logged online:
>
> Bug reference: 6141
> Logged by: michael
> Email address: mpa...@yahoo.com
> PostgreSQL version: 9.0
> Operating
Both queries use the same row's estimation and cost is comparable. But
execution time differs huge: 0.044s and 3100s. I think that the cost
of backward index scan is too small.
On 1/15/11, Tom Lane wrote:
> Tim Uckun writes:
>> I reported this in the pgsql-general list and was instructed to send