I read that the query planner changes with every release. Was there a
change from 8.4 to 9.3 that would account for a major (2 orders of
magnitude) difference in execution time for nested views after we upgraded
to 9.3?
Hi,
Please take this to another list, this has little to do with
PostgreSQL admin or performance.
Florent
On Tue, Feb 10, 2015 at 4:53 AM, sridhar bamandlapally
sridhar@gmail.com wrote:
In application code is
while inserting/updating: INSERT/UPDATE into ... ( '' ) - which is empty
No problem with this. If anyone want to specify more details.
But I want to know how far postgres can go. No matter OS or other variables.
Gavin, you got more than 12000 TPS?
2015-02-09 19:29 GMT-02:00 Gavin Flower gavinflo...@archidevsys.co.nz:
On 10/02/15 08:30, Luis Antonio Dias de Sá
I'd suggest you run it on a large ramdisk with fsync turned off on a 32 core
computer, see what you get, that will be a good indication of a maximum.
Keep in mind though that 'postgres' with fsync (vs. without) is such a
different creature that the comparison isn't meaningful.
Similarly
am connecting three tables in query. one table have 73000 records
another two tables have 138000 records.
but its take 12 sec for show 12402 rows in tables
Tables Structure:
Items Table
CREATE TABLE C_SAM_Master.items
(
itemno integer NOT NULL,
itemname character varying(250) NOT NULL,
On 10/02/15 10:29, Gavin Flower wrote:
On 10/02/15 08:30, Luis Antonio Dias de Sá Junior wrote:
Hi,
A survay: with pgbench using TPS-B, what is the maximum TPS you're
ever seen?
For me: 12000 TPS.
--
Luis Antonio Dias de Sá Junior
Important to specify:
1. O/S
2. version of PostgreSQL
3.
