801 reputation
39
bio website filip.rembialkowski.net
location Warsaw, Poland
age 38
visits member for 2 years, 6 months
seen Jan 13 at 19:23

A guy who loves fiddling with databases (especially PostgreSQL) and does it for a living. Strong GNU/Linux background, studied math for a while.


Dec
27
answered What is the equivalent of a “Certificate of Destruction” when using a cloud-hosted database?
Dec
27
comment Replication slave re-reading WAL on restart
What are your checkpoint_timeout and checkpoint_segments on master and slave? Did you know about restartpoints? postgresql.org/docs/current/static/wal-configuration.html
Dec
27
answered Can we use old primary to sync with standby after failover in PostgreSQL?
Nov
12
comment Stubborn autovacuum process slow things dows
Can you show output of SELECT version()?
Nov
12
comment Stored procedure deadlocking itself
It would be nice to reproduce your issue but the code does not compile. "IF NOT EXISTS (table from catalog)" - not correct. format() function - unknown. is it a standard Pg thing?
Oct
3
awarded  Yearling
Sep
17
awarded  Enlightened
Sep
17
awarded  Nice Answer
Mar
8
revised How many queries per second is my Postgres executing?
improve answer
Mar
8
revised How many queries per second is my Postgres executing?
improve answer
Mar
8
revised How many queries per second is my Postgres executing?
improve answer
Mar
7
answered How many queries per second is my Postgres executing?
Mar
3
comment “custom archiver out of memory” error when restoring large DB using pg_restore
This error says "463110542nd line after COPY video_data ... statement inside the dump is broken". You can try to convert the dump to a text file with pg_restore --clean --no-acl --no-owner -v db.dump -f db.txt. BTW - did you notice this big number is exactly 16 exabytes? This might be related to a bug in operating system / libs (google for similar bug reports).
Mar
3
awarded  Organizer
Mar
3
revised “custom archiver out of memory” error when restoring large DB using pg_restore
edited tags
Mar
1
comment “custom archiver out of memory” error when restoring large DB using pg_restore
"extra data after..." - this means malformed line in the dump. is it really your data? can you locate this offending row in the source database?
Feb
1
revised Good, Bad or Indifferent: WHERE 1=1
improve answer
Feb
1
comment Pgpool, Postgresql and Apache tuning (1000 concurrent spatial queries)
why "that pgPool is a configured as a load balancer suggests that this is all read-only"?
Feb
1
answered Good, Bad or Indifferent: WHERE 1=1
Oct
3
awarded  Yearling