ble?
With approach B the maximum number of rows could be about 200'000'000,
which sounds quite a lot …
Thanks a lot in advance for any suggestions!
Best regards,
Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
--
Sent via pgsql-perf
Mario Weilguni schrieb:
Andreas Hartmann schrieb:
[…]
I just verified that the autovacuum property is enabled.
[…]
Did you have:
stats_start_collector = on
stats_block_level = on
stats_row_level = on
Otherwise autovacuum won't run IMO.
Thanks for the hint! The section looks like
Guillaume Smet schrieb:
On Mon, Jul 21, 2008 at 1:25 PM, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
SELECT pg_database.datname,
pg_size_pretty(pg_database_size(pg_database.datname)) AS size
FROM pg_database where pg_database.datname = 'vvz_live_1';
da
Richard, thanks for your reply!
Richard Huxton schrieb:
Andreas Hartmann wrote:
Dear PostgreSQL community,
first some info about our application:
- Online course directory for a University
- Amount of data: complete dump is 27 MB
- Semester is part of primary key in each table
- Data for
nce with 2 and
10 semesters.
But since I'm not sure yet, I would very much appreciate any answers to
the following questions:
- Do you think the approach (reducing the data) is effective?
- Are there any particular tests which I should do?
Thanks a lot in advance!
-- Andreas
--
Andrea
