From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Casey Havenor <casey(at)myzip2it(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch file questions? |
Date: | 2011-06-29 20:03:41 |
Message-ID: | 1309377739-sup-1470@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Casey Havenor's message of mié jun 29 15:53:31 -0400 2011:
> Partitioning becomes impossible as I'd have to hunt down every single row
> from every table within the hierarchy when needed. I've got an object
> driven system with permissions for users so I'll easily have thousands of
> rows to manage across 100's of tables.
I suggest you raise this issue on pgsql-sql, -general or maybe
-performance, for design advice.
> Either way I'd still like to know how to apply a patch to PostgreSQL just to
> satisfy my curiosity? :)
You need the "patch" utility, and either the -p1 or -p0 switch depending
on how the file was built. When done, recompile.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-06-29 20:18:01 | Re: hint bit cache v6 |
Previous Message | Simon Riggs | 2011-06-29 19:54:00 | Re: Feature request: new column is_paused in pg_stat_replication |