Reputation
7,023
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 11 30
Newest
 Organizer
Impact
~314k people reached

1d
comment PostgreSQL 9.4.4 Crashing
was terminated by signal 9: so it does not crash, it's killed from outside. OOM is a plausible candidate indeed. You need to figure out what processes eat too much RAM; start with the kernel logs at the moment of the kill.
Aug
26
answered PostgreSQL trigger function that selects from %current% table
Aug
24
comment Using pipelined order by while fetching only first ten rows
from the doc: When using LIMIT, it is important to use an ORDER BY clause that constrains the result rows into a unique order. Otherwise you will get an unpredictable subset of the query's rows. Your query has that problem, fix that first.
Aug
22
answered pg_restore: [archiver] did not find magic string in file header
Aug
20
comment Postgres with no clients still chatty on network
See superuser.com/questions/856752/…
Aug
18
comment Step through multiple arrays in parallel with FOREACH
Explicit ROLLBACK in a function is not allowed and is the default outcome anyway. I would remove the entire exception block. What it does now is: in case of any error, report and raise the error. But this is just what happens when there's no custom exception handling.
Aug
18
comment Step through multiple arrays in parallel with FOREACH
The error looks like it has nothing to do with the question above. Please show your plpgsql code.
Aug
14
answered Adding new null column to table caused lock
Aug
12
answered json_array_elemnts() in FROM in postgresql 9.3 acting as where clause
Aug
11
answered Postgres 8.4 VACUUM FULL performance
Aug
7
comment Postgres 8.4 VACUUM FULL performance
You may look at VACUUM FULL as an ill-chosen name for a command that should be called COMPACT. VACUUM and COMPACT are different operations and you need the 1st one, not the 2nd.
Aug
7
comment Postgres 8.4 VACUUM FULL performance
See wiki.postgresql.org/wiki/VACUUM_FULL for 8.4 it lists the reasons why VACUUM FULL is not what you need now.
Aug
7
comment Postgres 8.4 VACUUM FULL performance
Leave out the FULL option. Also share the error message: is it database is not accepting commands to avoid wraparound data loss... or something else?
Aug
7
comment PostgreSQL bug(?) - logging with a minimum log level
@ErdincAy Logging only when errors occur is the default configuration. For your questions there's an entire doc page about it, please read it: postgresql.org/docs/current/static/runtime-config-logging.html
Aug
7
answered PostgreSQL bug(?) - logging with a minimum log level
Aug
5
comment How to reclaim space taken by an index that partially built and was terminated by a power outage
@dkitchel: that would be segments of 1Gb each for the huge index. Maybe check that their timestamps coincide with when the create index was running. As for deleting them, well, I hope my reasoning above is correct, but it's your data, so ultimately it's your decision!
Aug
5
revised How to reclaim space taken by an index that partially built and was terminated by a power outage
deleted 2 characters in body
Aug
5
answered How to reclaim space taken by an index that partially built and was terminated by a power outage
Aug
3
comment Postgres query plan has high rowcount, slow execution
I'm curious as to what values in table1 and table2 would make the original query produce any row at all. Isn't that query bogus to begin with?
Jul
30
comment Intentionally corrupting an index in PostgreSQL
user_indexes is an Oracle system view like pg_index. An index will be made invalid for instance by a bulk load that explicitly skips indexes. The status column is quite analogous to postgres indisvalid.