On 12/12/06, Tom Lane [EMAIL PROTECTED] wrote:
Axel Waggershauser [EMAIL PROTECTED] writes:
I tested different sizes on linux some time ago and found that 64KB
was optimal. But playing with different sizes again revealed that my
windows-linux problem seems to be solved if I use _any_ other
On 12/9/06, Tom Lane [EMAIL PROTECTED] wrote:
Axel Waggershauser [EMAIL PROTECTED] writes:
... This works quite well for the
following setups:
client - server
-
linux - linux
linux - windows
windows - windows
but pretty bad (meaning about 10 times slower
On 12/11/06, Thomas H. [EMAIL PROTECTED] wrote:
I'm out of ideas here, maybe someone could try to reproduce this
behavior or could point me to the thread containing relevant
information (sorry, maybe I'm just too dumb :-/)
please specify how you're transfering the data from windows - linux.
On 12/11/06, Tom Lane [EMAIL PROTECTED] wrote:
Yeah, that's what I couldn't think of the other day. The principal
report was here:
http://archives.postgresql.org/pgsql-general/2005-01/msg01231.php
By default, Windows XP installs the QoS Packet Scheduler service.
It is not installed by
Hi,
I have written my own 'large object'-like feature using the following table:
CREATE TABLE blob
(
id bigint NOT NULL,
pageno integer NOT NULL,
data bytea,
CONSTRAINT blob_pkey PRIMARY KEY (id, pageno)
)
WITHOUT OIDS;
ALTER TABLE blob ALTER COLUMN data SET STORAGE EXTERNAL;
CREATE
