531 reputation
24
bio website 2ndquadrant.us
location Baltimore, MD
age 43
visits member for 3 years
seen Sep 1 at 13:55

Database consultant for 2ndQuadrant; author of High Performance PostgreSQL 9.0.


Sep
1
comment What is the best approach to process huge amount of data insertion efficiently
Just so you know, 2 million records a day is not huge; it's a medium database insertion rate. That's 23 records a second. There are PostgreSQL servers that do a billion records a day. You can struggle even with this low amount if you try to do too much CPU heavy work in your triggers though. The advice you've gotten from Erwin already is taking you the right way.
Sep
1
answered How do I maintain high INSERT-performance on PostgreSQL
Sep
1
answered What's the best solution for offline db syncing
Dec
20
awarded  Yearling
Dec
20
awarded  Yearling
Nov
14
awarded  Revival
Oct
17
answered How to wait for PostgreSQL to be startable / restorable?
Oct
17
answered Proper storage size estimation technique for PostgreSQL
Oct
17
answered PostgreSQL Index Caching
Oct
17
answered High Availability for postgresql
Sep
15
comment Does PostgreSQL 9.1 Streaming Replication catch up after a lag without WAL archiving?
This answer is correct, but it highlights the problem. If you do ever pass wal_keep_segments, your replication is dead. Setting up file-based replication is not optional if you want a system that will survive a long disconnection from the master and catch back up.
Sep
15
answered Removing Archive Logs after PostgreSQL PITR online-recovery
May
10
answered How to know there is a maintenance job running on a postgresql database
May
10
answered Performance degradation while updating tables having 10s of millions of records
Feb
24
answered Fastest validation query in PostgreSQL
Feb
24
answered Database for building a realtime analytics system
Feb
24
answered Does running pg_dump on live db produce consistent backups?
Dec
20
awarded  Teacher
Dec
20
awarded  Supporter
Dec
20
comment New Job and Company uses PostgreSQL
It's possible to get the impression from what Scott wrote that the Windows version doesn't perform well because it's not being used/tuned in as many high performance installations. It's actually because there are architectural issues with how PostgreSQL runs on Windows that are at fault there.