Böckler Andreas wrote:
> I've played with seq_page_cost and enable_seqscan already, but you
> have to know the right values before SELECT to get good results ;)
The idea is to model actual costs on your system. You don't show
your configuration or describe your hardware, but you show an
estimate
On Wed, Oct 24, 2012 at 11:51 AM, Böckler Andreas wrote:
>>
>> Was there more to the plan that you snipped? If not, why isn't it
>> checking all the other partitions?
>
> Your right. It's checking all partitions!. So the constraint exclusion
> doesn't kick in.
> This can be fixed with
> SELECT
>
On Thu, Oct 25, 2012 at 9:47 AM, Shaun Thomas wrote:
>> ... as long as the rsync was bracketed by calls to pg_start_backup()
>> and pg_stop_backup().
>
>
> Or they took it during a filesystem snapshot, or shut the database down.
>
> I thought that the only thing start/stop backup did was mark the
On 10/25/2012 07:10 AM, Kevin Grittner wrote:
... as long as the rsync was bracketed by calls to pg_start_backup()
and pg_stop_backup().
Or they took it during a filesystem snapshot, or shut the database down.
I thought that the only thing start/stop backup did was mark the
beginning and end
Shaun Thomas wrote:
> Update the config and start as a slave, and it's the same as a
> basebackup.
... as long as the rsync was bracketed by calls to pg_start_backup()
and pg_stop_backup().
-Kevin
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to
