On Thu, Nov 11, 2010 at 1:25 PM, Kyriacos Kyriacou
wrote:
> This is my first post in this mailing list and I would like to raise an
> issue that in my opinion is causing performance issues of PostgreSQL
> especially in a transaction processing environment. In my company we are
> using PostgreSQL f
Yes, since (sample_id, drone_id) is primary key, postgres created
composite index on those columns. Are you suggesting I add two more
indexes, one for drone_id and one for sample_id?
(sample_id,drone_id) covers sample_id but if you make searches on drone_id
alone it is likely to be very s
realm_51=# vacuum analyze verbose drones;
INFO: vacuuming "public.drones"
INFO: scanned index "drones_pk" to remove 242235 row versions
DETAIL: CPU 0.02s/0.11u sec elapsed 0.28 sec.
INFO: "drones": removed 242235 row versions in 1952 pages
DETAIL: CPU 0.01s/0.02u sec elapsed 0.03 sec.
INFO:
On Mon, 29 Nov 2010, AI Rumman wrote:
Oh! Actualy it is:
select replace('Dhaka University of Bangladesh:*', ' ',':* & ');
No space at start.
So, what are actual problems with full text ? I mostly interesting with
server crush. We need test data, test query and error message.
On Mon, Nov
Just a general note re the subject, I've also had troubles with
postgres being unable to optimize a query with OR. The work-around,
although a bit messy, was to use a UNION-query instead.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscr
Oh! Actualy it is:
select replace('Dhaka University of Bangladesh:*', ' ',':* & ');
No space at start.
On Mon, Nov 29, 2010 at 6:37 PM, Oleg Bartunov wrote:
> What does replace(' Dhaka University of Bangladesh:*', ' ',':* & ') means ?
> I see it produces something wrong for to_tsquery:
>
> test=
What does replace(' Dhaka University of Bangladesh:*', ' ',':* & ') means ?
I see it produces something wrong for to_tsquery:
test=# select replace(' Dhaka University of Bangladesh:*', ' ',':* & ');
replace
---
:* & Dhaka:*
On 11/29/2010 08:11 AM, Mark Kirkwood wrote:
On 29/11/10 00:46, Mario Splivalo wrote:
This is the slow part:
INSERT INTO drones_history (sample_id, drone_id, drone_log_notice,
drone_temperature, drone_pressure)
SELECT * FROM tmpUpdate;
For 100 rows this takes around 2 seconds. For 1000 rows th
On 11/28/2010 10:50 PM, Pierre C wrote:
I pasted DDL at the begining of my post.
Ah, sorry, didn't see it ;)
The only indexes tables have are the ones created because of PK
constraints. Table drones has around 100k rows. Table drones_history
has around 30M rows. I'm not sure what additional
