Em 25-03-2011 17:59, DIEGO BALAN escreveu:
aparece a mensagem "please provide a password for the database superuser and
service account. if the service account already exists in windows, you must
enter the current password for the account. if the account does not exist,
it will be created when yo
"martin van leeuwen" wrote:
> PostgreSQL version: 9.0.2-1-win-x84
> Operating system: windows 7 enterprise SP1
> Description: pgadmin sql-query text pad doesn't work
> Details:
>
> The text input for sql query tool in pgadmin stopped working today
> (26 mrch 2011) and was succesfully used the l
"YAMAMOTO Takashi" wrote:
> Description: SetRWConflict assertion failure
> SerializableXactHashLock relocking in CheckTargetForConflictsIn()
> seems racy to me.
You're right. The attached patch should fix the assertion you hit.
I will take a close look at the code above the patched area (
On Fri, Mar 25, 2011 at 4:48 PM, Tom Lane wrote:
> Greg Stark writes:
>> On Fri, Mar 25, 2011 at 7:43 PM, Tom Lane wrote:
>>> I don't recall any particular discussion of making the user contend with
>>> that. My thought would be to do something like enlarging the table by
>>> 10% anytime we nee
On Fri, Mar 25, 2011 at 5:56 PM, Tom Lane wrote:
> Christopher Browne writes:
>> What seems natural-ish to me might include:
>> - Stomping a bit on the FSM replacement to make sure nobody's going to
>> be writing to the later extensions;
>> - Watching free space during the process so the "first"
Robert Haas writes:
> I think we've had a number of pieces of evidence that suggest that
> extending 8kB at a time is too costly, but I agree with Greg that the
> idea of extending an arbitrarily large table by 10% at a time is
> pretty frightening - that could involve allocating a gigantic amount
