Hello,
I was attempting to calculate the actual occupied space by a Table.
Below is what i did -
I summed up the avg_width of each column of a table from pg_stats, which
gives me the average size of a row (277 bytes).
select* sum(avg_width) as average_row_size from pg_stats *where
On Wed, Oct 5, 2011 at 2:38 PM, Venkat Balaji venkat.bal...@verse.inwrote:
Hello,
I was attempting to calculate the actual occupied space by a Table.
Below is what i did -
I summed up the avg_width of each column of a table from pg_stats, which
gives me the average size of a row (277
Venkat Balaji venkat.balaji 'at' verse.in writes:
Hello,
I was attempting to calculate the actual occupied space by a Table.
SELECT relname, reltuples, pg_size_pretty(relpages*8*1024) as size FROM
pg_class, pg_namespace WHERE pg_namespace.oid = pg_class.relnamespace AND
relkind = 'r' AND
On Wed, Sep 21, 2011 at 11:57 AM, Greg Smith g...@2ndquadrant.com wrote:
On 09/21/2011 12:13 PM, Venkat Balaji wrote:
I as a DBA, suggested to perform VACUUM FULL and RE-INDEXING + ANALYZE to
ensure that IO performance and Indexing performance would be good
Read
Scott Marlowe scott.marl...@gmail.com writes:
It used to be that cluster on a very randomly ordered table was much
slower than doing something like select * into newtable from oldtable
order by col1, col2; Is that still the case in 9.0/9.1?
Fixed in 9.1, per release notes:
* Allow
I ran a test using Intel's timed workload wear indication feature on a
100G 710 series SSD.
The test works like this : you reset the wear indication counters, then
start running
some workload (in my case pgbench at scale 100 for 4 hours). During the
test run
a wear indication attribute can
Stephen Frost wrote:
-- Start of PGP signed section.
* Robert Schnabel (schnab...@missouri.edu) wrote:
And getting back to the to-do list entry and reading the related
posts, it appears that even if you could set work_mem that high it
would only use 2GB anyway. I guess that was the second
Hello,
Has any performance or evaluation done for pg9.x streaming replication
over WAN ?
How adequate is the protocol to push WALs over long distance ?
Any best practice tuning wal_* for WAN ?
Cheers,
Ben-
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make
