Quoting "Simon Riggs" :
Use Rules is the current answer, though that has other issues also.
Hi Simon - as you say, Rules have issues. From my understanding,
partitioning with rules is impractical.
Anyway, thanks for clarifying.
Cheers
Henry
--
Sent via pgsql-general mailing list (pgsql-
I have to say, that this 'feature' also annoys me.
at least ability to update row count would be appreciated. Not to
mention proper partitioning, but that requires quite few changes in
the guts.
Currently there was a guy offering patch that adds partitioning, but
it uses built in trigger, which is
On Mon, 2009-04-06 at 09:57 +0200, Henry wrote:
> Is this weirdness scheduled to be addressed in 8.4, or is there some
> other hack I can try (without changing all SQL), or is the *only*
> solution to mess with existing (working) front-end code to work around
> this issue?
No, not in 8.4
Greetings,
I recently successfully partitioned a 100+GB table into many smaller
ones for improved select performance, etc. This works extremely well,
I must say. SELECTs, UPDATEs and DELETEs are handled automatically by
Pg, my trigger takes care of distributing INSERTs, etc.
Only proble
