256 was set some time when we were testing a differnt issue. I read that
the only drawback is the amunt of time required for recovery, which was
tested and it was like 10 seconds for the 256 segments, and higher values
mean less disk usage.
Anyway all these parameters should affect the throughput t
On Tue, Jul 30, 2013 at 8:35 AM, German Becker wrote:
> 256 was set some time when we were testing a differnt issue. I read that
> the only drawback is the amunt of time required for recovery, which was
> tested and it was like 10 seconds for the 256 segments, and higher values
> mean less disk us
Hi All;
A client's master database crashed, they tried to startup the streaming
replication slave and it refuses to start.
See the log details below... thanks in advance for any help
Master log:
2013-07-30 16:23:01 MDT PANIC: corrupted page pointers: lower = 0, upper
= 0, special = 0
Hi,
I have a Windows box running Windows Server 2003 Enterprise Edition Service
Pack 2 with PostgreSQL 8.2.23 and getting a server crash while trying to
select a table:
select * from "TOTALL.tt_est" where assina=' kdkd' ;
Dumping the table with pg_dump or creating indexes in this table produce
t
