omething that would meet my requirements above?
Steve Pritchard
British Trust for Ornithology, UK
as a PDF).
All working out well in testing at the moment.
Steve Pritchard
British Trust for Ornithology
On 23 September 2015 at 17:36, Israel Brewster
wrote:
>
> With my application servers, I have a system set up using corosync and
> pacemaker that allows for seamless fail-over bet
M FULL, which I expect to reduce table_len.
Steve
On 23 September 2015 at 17:50, Tom Lane wrote:
> Steve Pritchard writes:
> > -- Average length of a row in bytes:
> > select avg(octet_length(t.*::text)) FROM observation t;
> > -- 287 bytes
>
> That measurement t
h(t.*::text)) FROM observation t;
-- 287 bytes
-- Number of rows * average size of row:
select pg_size_pretty(count(obs_id) * 287) from observation;
-- 9.4 GB
If the live tuples take 9.4GB, then dead ones take 1.2GB = 10.6GB total.
What accounts for the remaining 9.4GB? (20GB - 10.6GB)
Steve Pritchard
British Trust for Ornithology
