=?iso-2022-jp?B?GyRCMEJAPiEhRD5MaRsoQg==?=
writes:
> I have checked latest source code.
> But, backward scan doesn't work correctly...
[ pokes at that... ] Hmm, the patches I applied a couple days ago
assumed that we are stepping forward or back from a place where the
WHERE clauses are satisfie
>>
>> Hello,
>>
>> In the newest PostgreSQL(9.1.1) or lower, Index-Scan's actual time may
>> increase unexpectedly.
>>
>> I think that this is for scanning All NULL VALUES when performing an
>> indexscan
>> even if they does not need to be scanned.
>
>I think this was just fixed. Please check lates
On 11/02/2011 01:53 AM, Jim Jackson wrote:
The following bug has been logged online:
Bug reference: 6281
Logged by: Jim Jackson
Email address: jimjack...@judgefite.com
PostgreSQL version: ??
Operating system: Windows 7
Description:need to remove
Details:
I need to
Hi Mark
Thanks for your suggestions (and Robert and Guillaume). I will try the
overcommit_memory=2 idea out in a couple of weeks. At the moment I am
running everything on 8.4.8, which is working great, and have pressing
deadlines looming (next Wednesday).
I'll let you know when I do. I want t
Hi Magnus & Heiki,
The above problem solved when I have connected 8.1 server through PgAdmin
III OF 9.1 version and restored.
So, I think there was some bug fix related to the above problem in PgSql 9.1
pg_restore.exe.
This is for your reference and information.
Thanks and regards,
Sathees
The following bug has been logged online:
Bug reference: 6281
Logged by: Jim Jackson
Email address: jimjack...@judgefite.com
PostgreSQL version: ??
Operating system: Windows 7
Description:need to remove
Details:
I need to remove the postgres from my PC. it does not
