Tom Lane wrote:
I wouldn't mind seeing people be a little more vocal on the hackers list
about what they plan to be doing, just so that there's not duplication
of effort.
Stuff I have done in some form that I need to finish up and submit:
- GiST improvements: sane memory management, 10% scan perf.
hello,
I tested you patch, and it's good work. I would all methods in PostgreSQL.
I found query which kill backand
WITH t AS (
SELECT 0::int AS i
UNION ALL SELECT i + 1 FROM t WHERE i < 100)
SELECT * FROM t;
Regards
Pavel Stehule
---(end of broadcast)
Hi!
The new snpritnf code appears not to deal with 64-bit ints. I'm getting
failures on win32 for int8 as well as all the time related tests (win32
uses int8 for tinmestamps). Removing the snprintf code and falling back
to the OS code makes everything pass again.
I would guess this affects int8 e
I'd like to see this one also considered for 8.0.x, though I'd certainly
like to see some more testing as well. Perhaps it's suitable for the
"8.0.x with extended testing" that is planned for the ARC replacement
code?
It does make a huge difference on win32. While we definitly don't want
to risk d
Magnus Hagander wrote:
Magnus Hagander wrote:
> Magnus prepared a trivial patch which added the O_SYNC flag
> for windows and mapped it to FILE_FLAG_WRITE_THROUGH in
> win32_open.c.
[snip]
Michael Paesold wrote:
The original patch did not have any documentation. Have you
added some? Since this has
Bruce Momjian wrote:
Patch applied. Thanks.
I assume this is not approprate for 8.0.X.
---
Magnus Hagander wrote:
> Magnus prepared a trivial patch which added the O_SYNC flag
> for windows and mapped it to FILE_FLAG_WRITE_THROUGH in
> wi
>> Patch applied. Thanks.
>>
>> I assume this is not approprate for 8.0.X.
>>
>> ---
>>
>>
>> Magnus Hagander wrote:
>>> > Magnus prepared a trivial patch which added the O_SYNC flag
>>> > for windows and mapped it to FILE_FLAG_WRITE_THRO
Jeff Davis wrote:
The only reason I did that was because the original source was difficult
to read and work on. Is there a reason that code and comments wrap
around to the next line throughout the file?
I'm not sure what you mean. Assuming your editor expand tabs to 4 spaces
(which is the conventi
