On Fri, Apr 19, 2013 at 11:17 AM, Christopher Browne wrote:
>
> I would expect the strategy you have in mind to be more useful to apply at
> the filesystem level, so that it's not in Postgres altogether. (Ala
> "Stacker", remember DR-DOS?)
>
> But, to speak arguable heresy, the demerits of this s
I would expect the strategy you have in mind to be more useful to apply at
the filesystem level, so that it's not in Postgres altogether. (Ala
"Stacker", remember DR-DOS?)
But, to speak arguable heresy, the demerits of this sort of thing are
described nicely in Another Database's Documentation: <
On Fri, Apr 19, 2013 at 10:17 AM, Will Childs-Klein wrote:
> Hello All,
> I'm writing today to inquire about finding the exact point in the source
> where postgres writes to disk. I'm trying to implement some compression in
> postgres. The idea is to compress the data right when its written to dis
Will,
* Will Childs-Klein (willc...@gmail.com) wrote:
> I'm writing today to inquire about finding the exact point in the source
> where postgres writes to disk. I'm trying to implement some compression in
> postgres.
PostgreSQL already does compression in most cases where you'd want it
done..
