Reputation
5,690
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 9 28
Newest
 Enlightened
Impact
~243k people reached

13h
comment postgresql + pgbouncer, idle server and high cl_waiting
So max_connections in postgresql.conf has been left to its default 100 ?
22h
answered Minimal grants for readonly single-table access on PostgreSQL
Apr
24
awarded  Enlightened
Apr
24
awarded  Nice Answer
Apr
24
comment missing WAL file on standby server following a backup
Yes, the restore_command is needed and the live server must not copy directly into $PGDATA/pg_xlog on the standby. It must copy into the archive directory. Only restore_command is allowed to copy into pg_xlog and only on demand (when postgres calls it).
Apr
24
answered missing WAL file on standby server following a backup
Apr
24
reviewed Approve How to move a specific Postgres database to different harddrive?
Apr
24
reviewed Approve how to disable and enable SSIS package using commandline?
Apr
21
answered pg_ctl status responds with “available” during failed startup
Apr
15
answered Insertion Rule on a view
Apr
11
answered Last occurance of time relative to now()
Apr
10
awarded  Nice Answer
Apr
10
comment no pg_hba.conf entry for replication connection from host
@picardo: the error is understandable, because the pg_hba.conf filter comes first. If the user/db/host/origin combination doesn't match any line in pg_hba, it doesn't even check if the user and db exist. And if it did report it in the error message, that would be leaking information to unauthorized clients and wrong as such.
Apr
9
answered no pg_hba.conf entry for replication connection from host
Apr
9
answered pg_basebackup fails with “ too many connections for role ”replication“”
Apr
8
comment pg_basebackup fails with “ too many connections for role ”replication“”
Check pg_roles.rolconnlimit for rolname='replication'
Apr
5
reviewed Close SQL Server : Index Seek with very high Scan Count
Apr
5
reviewed Leave Open Performance of MySQL BLOB fields processing
Apr
5
comment Performance of MySQL BLOB fields processing
Yes you should consider splitting the contents into smaller pieces. Updating part of a field does not exist in SQL. Changing one character means duplicating/rewriting the entire field. It will also tend to allocate memory for the entire field anytime it has anything to do with it.
Mar
28
awarded  postgresql