Am 28. Mai 2015 17:15:22 MESZ, schrieb Ravi Krishna :
>I am testing partitioning of a large table. I am INHERITING child
>tables.
>It is using a range
>partitioning based on a sequence col, which also acts as the primary
>key. For inserts I am using a trigger which will redirect insert to
>the ri
Am 28. Mai 2015 18:25:42 MESZ, schrieb Ravi Krishna :
>> Have you set up constraints on the partitions? The planner needs to
>know
>> what is in the child tables so it can avoid scanning them.
>
>Yes. each child table is defined as follows
>
>CREATE TABLE TSTESTING.ACCOUNT_PART1
>
> ( CHECK (ACCO
Am 2015-06-03 19:00, schrieb Daniel Begin:
Sorry, my question might not have been clear…
I set myself the temp_tablespace to that location but did not expect
the drive could get full;
Multiple factors may have caused the drive to turn off (not
necessarily postgresql);
So, if that temp_tablespa
Am 2015-06-08 14:45, schrieb otheus uibk:
The manual and in this mailing list, the claim is made that
consistent, file-level backups may be made by bracketing the
file-copy
operation with the postgresql pg_start_backup and pg_stop_backup
operations. Many people including myself have found that
Am 2015-07-03 13:00, schrieb howardn...@selestial.com:
On 03/07/2015 11:39, Guillaume Lelarge wrote:
> In that case is there any recommendation for how often to make
base backups in relation to the size of the cluster and the size of
the WAL?
>
Nope, not really. That depends on a lot of thi
That seems to be a large drop. On the other hand 13 ms is also like a very
large network latency. On LAN your usually in the sub ms area. So going from
e.g. 0.2 ms to 13ms is 65 fold decrease. What is the network toplogy like?
Jan
Von meinem iPad gesendet
> Am 24.07.2015 um 18:59 schrieb Chris
; 5000tps
>>
>> When I do it from a server that has a 13ms ping latency, it drops to 37tps.
>>
>> This is using the default pgbench script, is it to be expected?
>> If so, why?
>>
> Am 24.07.2015 um 20:06 schrieb Jan Lentfer :
>
> That seems to be a
