Reputation
8,292
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 12 31
Newest
 Nice Answer
Impact
~413k people reached

10h
answered pgAdmin is extremely slow on any remote operation
Feb
3
answered Plpgsql (Postgres) function for sanity check
Feb
1
revised dumping database with “compressed data is corrupt” errors
added 659 characters in body
Feb
1
answered dumping database with “compressed data is corrupt” errors
Jan
26
answered What are the limits of Postgresql's large object facility?
Jan
23
answered How to paste chinese characters in psql terminal?
Jan
21
comment errors install and start postgresql-9.5
I would try the opposite and use apt-get interactively to see what's in that dialog it wants to display. Anyway FWIW I can't reproduce your problem when installing 9.5.0-1.pgdg14.04+2 but it's 14.04 (no longer have 12.04 personally).
Jan
21
comment Upgrade PostgreSQL 9.4 to 9.5 : LC_ALL unset
LC_CTYPE=en_US.UTF-8 shadows the LC_CTYPE pre-existing in the environment, which appears to be set to UTF-8 according to Perl's error output. Unlike most programs that will just ignore it, postgres' initdb will fail outright on a non-existing locale. The root cause is a rogue LC_CTYPE="UTF-8" somewhere in your init/environment scripts.
Jan
21
comment errors install and start postgresql-9.5
Yes, see the output lines starting with debconf.
Jan
21
comment errors install and start postgresql-9.5
The 9.5 server actually starts during apt-get install, but for a reason that is not apparent in the logs, debconf thinks it failed. Except if the reason was it couldn't find a controlling tty, since it complains about that.
Jan
14
comment What determines whether `pg_dump` includes a varchar length?
If the length exists, it gets included. I'd bet a beer that your devs are not dumping the same schema.
Jan
11
revised PostgreSQL: Restoring 1 file from a directory format dump
added 298 characters in body
Jan
11
comment PostgreSQL: Restoring 1 file from a directory format dump
@Brooks: the contents of one table can be displayed with pg_restore --table=tablename.
Jan
11
answered PostgreSQL: Restoring 1 file from a directory format dump
Dec
30
answered postgresql.conf file found in both /usr/share/postgresql and /etc/postgresql/
Dec
23
answered PostgreSQL force sslmode=verify-full
Dec
9
comment Update by iterating table in batches faster than whole table in PostgreSQL
Also you could try EXPLAIN of the query and compare with and without the BETWEEN clause. See how the execution plan differs and if the plan without BETWEEN is reasonable or not.
Dec
9
comment Update by iterating table in batches faster than whole table in PostgreSQL
Sorry for the negativity, but I think both #1 and #2 are completely wrong. #1 because the update mostly happens on disk, not in memory (in fact it's a strong point of PG compared to others dbs to be able to do large updates without needing much resources). #2 because a function runs inside a single transaction so any cost associated to a transaction would be the same anyway.
Dec
9
comment Update by iterating table in batches faster than whole table in PostgreSQL
Maybe the big update was just waiting for a lock held by another session. If you can reproduce it next time check out the queries at wiki.postgresql.org/wiki/Lock_Monitoring
Dec
8
comment Get max url from PostgreSQL statement
@Erik: the last you found discriminates among its inputs by keeping only the last one. But the inputs are presented to it in an order that is not guaranteed by anything in SQL. That's why this last is not built-in, contrary to max or min: it's not deterministic.