[GENERAL] Trading off large objects (arrays, large strings, large tables) for timeseries

2005-02-15 Thread Antonios Christofides
My questions briefly: (1) I made experiments with large (millions of rows/elements) arrays of text (text[], each element is 20-30 characters). On 7.4 (Debian Sarge prepackaged), inserting such an array takes forever (10 thousand elements per minute), but accessing, or writing an el

Re: [GENERAL] Trading off large objects (arrays, large strings, large tables) for timeseries

2005-02-16 Thread Antonios Christofides
Tom Lane wrote: > Antonios Christofides <[EMAIL PROTECTED]> writes: > > Why 25 seconds for appending an element? > > Would you give us a specific test case, rather than a vague description > of what you're doing? OK, sorry, here it is (on another machine, thus ti

Re: [GENERAL] Trading off large objects (arrays, large strings, large tables) for timeseries

2005-02-16 Thread Antonios Christofides
Shridhar Daithankar wrote: > Perhaps you could attempt to store a fix small number of records per row, say > 4-6? Or may be a smaller fixed size array, That should make the row overhead > less intrusive... Thanks, I didn't like your idea, but it helped me come up with another idea: (timeser

[GENERAL] Is Win32 port good for operational use?

2004-10-04 Thread Antonios Christofides
Hi, I know we will be using at our own risk, I have read the "experimental" warnings, but still PostgreSQL is a very attractive RDBMS for the Windows application we are developing. Most customers will want a simple single-machine version, where the program will be storing its data in a local datab