Description:
How to Speed up SQL Queries and the PostgreSQL Server
|
|
|
error while upgrading form 9.1 to 9.2
|
| |
Hello all,
we are getting struck with this error while upgrading while upgrading from 9.1 to 9.2
-bash-4.1$ clear
-bash-4.1$ /usr/pgsql-9.2/bin/pg_upgrade -c --old-datadir=/var/lib/pgsql/9 .1/data --new-datadir=/var/lib/pgsql/9 .2/data --old-bindir=/usr/pgsql-9.1/bi n --new-bindir=/usr/pgsql-9.2/bi n... more »
|
|
|
template1 vacumming
|
| |
Hi,
My databases are updated regularly so I am vacuuming frequently (every one hour). Recently i also added template1 database to avoid over wrapping problem. But somehow i am seeing strange behavior.
Most of the time all db vacuuming finish in 30 secs. but once in a day or two
- My actual DB is taking less than 30 secs for vacuuming.... more »
|
|
|
Postgres individual inserts, slow performance, delay
|
| |
I'm just trying to insert a couple of rows. I need them committed right away. And there will be a brief delay before the next inserts are ready.
Sample python program:
[link]
I simulate the delay in my sample program by sleeping for 0.2 sec. You can see by the output that sometime the inserts are fast and sometimes close to 0.2 sec.... more »
|
|
|
Performance ts_vector fulltext search
|
| |
...
When I try that I get
ERROR: column "to_tsvector('italian'::regcon fig, "What"::text)" does not exist
as indeed I should, because you seem to be confused about SQL quoting
rules --- that whole expression is being taken as a name. However, the
bigger problem here is that you're creating btree indexes, which are not... more »
|
|
|
Postgres log(pg_logs) have lots of message
|
| |
Hi,
Could some please explain what these warnings mean in postgres.
I see these messages a lot when automatic vacuum runs.
1 tm:2013-04-10 11:39:20.074 UTC db: pid:13766 LOG: automatic vacuum
of table "DB1.nic.pvxt": could not (re)acquire exclusive lock for truncate
scan
1 tm:2013-04-10 11:40:22.849 UTC db: pid:14286 LOG: automatic vacuum... more »
|
|
|
Postgresql.conf file from like 7.x to 9.2
|
| |
Afternoon
So I just realized I've been just reimporting me Postgres configs from one
version to the next, since they were initially customized for my setup.
Maybe from 7.x... And now on 9.2.4
Is there an easy/clean way to adapt my old config file to the new stuff,
I'm not sure what all has changed, so wondering if I just have to go line... more »
|
|
|
slow bitmap heap scans on pg 9.2
|
| |
I'm encountering an issue where PG 9.2.4 (we also see this with 9.2.3) is picking a plan involving a bitmap heap scan that turns out to be much slower than a nested-loop plan using indexes.
The planner picks the hashjoin plan by default (see attached files)
Bitmap Heap Scan on public.table_b_2 b (cost=172635.99..9800225.75... more »
|
|
|
slow joins?
|
| |
On 9.2.4, running two identical queries except for the value of a column in
the WHERE clause. Postgres is picking very different query plans, the first
is much slower than the second.
Any ideas on how I can speed this up? I have btree indexes for all the
columns used in the query.
explain analyze... more »
|
|
|
INDEX Performance Issue
|
| |
Hi All,
Hoping someone can help me out with some performance issues I'm having with
the INDEX on my database. I've got a database that has a data table
containing ~55,000,000 rows which have point data and an area table
containing ~3,500 rows which have polygon data. A user queries the data by... more »
|
|
|
