Peripheral Links

• Home
• About
• Download
• Documentation
• Community
• Developers
• Support
• Your account

pgsql-performance - March 2009

2009-03-01

• "slow" queries Brian Cox (02:51)
• Re: "slow" queries Robert Haas (03:15)
• Re: Bad plan for nested loop + limit Robert Haas (03:32)
• Re: "slow" queries Tom Lane (17:05)
• Re: TCP network cost Linos (17:32)
• Re: TCP network cost Tom Lane (17:43)
• Re: TCP network cost Linos (17:57)
• Re: TCP network cost Tom Lane (18:10)
• Re: TCP network cost Linos (18:19)
• Re: TCP network cost Tom Lane (18:28)
• Re: TCP network cost Magnus Hagander (18:40)
• Re: TCP network cost Linos (18:52)
• Re: "slow" queries Cox, Brian (19:21)

2009-03-02

• Re: "slow" queries Tom Lane (01:57)
• Re: "slow" queries Brian Cox (18:22)
• Re: "slow" queries Scott Carey (18:58)
• Re: "slow" queries Robert Haas (19:04)
• Re: "slow" queries Tom Lane (19:29)
• Re: "slow" queries Brian Cox (19:55)
• Re: "slow" queries Tom Lane (20:11)
• Re: "slow" queries Brian Cox (20:36)
• Re: "slow" queries Tim Bunce (21:24)
• Re: "slow" queries Scott Marlowe (21:59)

2009-03-03

• Postgres 8.3, four times slower queries? Aaron Guyon (00:18)
• Re: Postgres 8.3, four times slower queries? Tom Lane (03:23)
• Substring search using "exists" with a space in the search term Hans Liebenberg (12:12)
• Problems with ordering (can't force query planner to use an index) Sebastjan Trepca (17:05)
• Re: Problems with ordering (can't force query planner to use an index) Robert Haas (17:12)
• Re: Problems with ordering (can't force query planner to use an index) Sebastjan Trepca (17:20)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (17:31)
• Re: Problems with ordering (can't force query planner to use an index) David Wilson (17:34)
• Re: Postgres 8.3, four times slower queries? david (17:38)
• Re: Problems with ordering (can't force query planner to use an index) Sebastjan Trepca (17:40)
• Re: Problems with ordering (can't force query planner to use an index) Robert Haas (17:40)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (17:52)
• Re: Problems with ordering (can't force query planner to use an index) Sebastjan Trepca (19:05)
• Re: Problems with ordering (can't force query planner to use an index) Sebastjan Trepca (19:16)
• Re: Problems with ordering (can't force query planner to use an index) Robert Haas (20:27)
• Re: Problems with ordering (can't force query planner to use an index) Tom Lane (21:27)
• Re: Postgres 8.3, four times slower queries? Tom Lane (22:34)

2009-03-04

• work_mem in high transaction rate database Flavio Henrique Araque Gurgel (00:28)
• Re: work_mem in high transaction rate database Scott Marlowe (01:37)
• Re: work_mem in high transaction rate database Akos Gabriel (07:04)
• Re: work_mem in high transaction rate database Dimitri Fontaine (09:16)
• Re: work_mem in high transaction rate database Flavio Henrique Araque Gurgel (12:46)
• Long Running Commits Brad Nicholson (16:18)
• Re: work_mem in high transaction rate database Scott Carey (18:18)
• Re: work_mem in high transaction rate database Scott Marlowe (21:49)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (23:20)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (23:42)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (23:42)

2009-03-05

• Re: Postgres 8.3, four times slower queries? Robert Haas (13:21)
• Index scan plan estimates way off. Jonathan Hseu (15:56)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (16:06)
• Re: Postgres 8.3, four times slower queries? Robert Haas (16:56)
• Re: Index scan plan estimates way off. Tom Lane (18:30)
• Re: Postgres 8.3, four times slower queries? Kevin Grittner (18:57)
• Re: Postgres 8.3, four times slower queries? Robert Haas (19:15)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (19:58)

2009-03-06

• Re: Index scan plan estimates way off. Jonathan Hseu (01:42)
• Re: Index scan plan estimates way off. Robert Haas (02:33)
• Re: Postgres 8.3, four times slower queries? Aaron Guyon (15:50)

2009-03-09

• Query much slower when run from postgres function Mario Splivalo (13:36)
• DBT Presentation Location? Lee Hughes (14:28)
• Re: Query much slower when run from postgres function Tom Lane (16:31)
• Re: [PERFORM] Query much slower when run from postgres function Guillaume Cottenceau (16:51)
• Re: [PERFORM] Query much slower when run from postgres function Guillaume Smet (17:04)
• Re: [PERFORM] Query much slower when run from postgres function Tom Lane (17:16)
• Re: [PERFORM] Query much slower when run from postgres function Andreas Wenk (17:42)
• Re: Query much slower when run from postgres function Mario Splivalo (19:13)
• Re: [PERFORM] Query much slower when run from postgres function Mario Splivalo (19:26)
• Re: Query much slower when run from postgres function Tom Lane (19:51)
• Re: [PERFORM] Query much slower when run from postgres function Dave Cramer (19:56)
• Re: [PERFORM] Query much slower when run from postgres function James Mansion (20:35)
• Re: [PERFORM] Query much slower when run from postgres function Scott Carey (20:56)
• Re: [PERFORM] Query much slower when run from postgres function Oliver Jowett (21:31)
• Re: [PERFORM] Query much slower when run from postgres function Oliver Jowett (21:40)
• Re: Query much slower when run from postgres function Mario Splivalo (22:13)
• Re: Query much slower when run from postgres function Tom Lane (23:36)

2009-03-10

• Re: DBT Presentation Location? Mark Wong (00:57)
• Re: [PERFORM] Query much slower when run from postgres function Scott Carey (03:38)
• Re: [PERFORM] Query much slower when run from postgres function Guillaume Cottenceau (08:05)
• Re: [PERFORM] Query much slower when run from postgres function Oliver Jowett (08:39)
• Re: [PERFORM] Query much slower when run from postgres function Guillaume Cottenceau (09:41)
• When does sequential performance matter in PG? henk de wit (14:09)
• Re: When does sequential performance matter in PG? Matthew Wakeling (14:28)
• Re: Query much slower when run from postgres function Frank Ch. Eigler (14:40)
• Re: When does sequential performance matter in PG? henk de wit (14:57)
• Re: [PERFORM] Query much slower when run from postgres function Kris Jurka (16:55)
• Re: Query much slower when run from postgres function Tom Lane (17:20)
• Re: When does sequential performance matter in PG? Greg Smith (17:50)
• Re: When does sequential performance matter in PG? Scott Carey (18:01)
• Query performance over a large proportion of data Steve McLellan (21:12)
• Re: Query performance over a large proportion of data Scott Marlowe (21:57)
• Re: Query performance over a large proportion ofdata Kevin Grittner (22:06)
• Re: Query performance over a large proportion of data Scott Marlowe (23:19)

2009-03-11

• Re: Query performance over a large proportion of data Tom Lane (00:09)
• Re: Query performance over a large proportion of data Tom Lane (00:16)
• Re: Query performance over a large proportion of data Steve McLellan (03:15)
• Re: Query performance over a large proportion of data Steve McLellan (03:21)
• Re: Query performance over a large proportion of data Steve McLellan (03:30)
• Re: Query performance over a large proportion of data Scott Marlowe (04:53)
• random_page_cost vs ssd? Jeff (13:46)
• Re: random_page_cost vs ssd? Grzegorz Jaśkiewicz (15:37)
• Re: random_page_cost vs ssd? Scott Carey (17:06)
• Re: random_page_cost vs ssd? Andrej (19:04)
• Full statement logging problematic on larger machines? Frank Joerdens (19:27)
• Re: random_page_cost vs ssd? Scott Carey (19:28)
• Re: random_page_cost vs ssd? hubert depesz lubaczewski (19:32)
• Re: random_page_cost vs ssd? Kevin Grittner (19:40)
• Re: Full statement logging problematic on larger machines? Scott Marlowe (19:41)
• Re: random_page_cost vs ssd? Scott Carey (20:31)
• Re: Full statement logging problematic on larger machines? Tom Lane (20:46)
• Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (20:53)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (22:27)
• Re: Full statement logging problematic on larger machines? Frank Joerdens (22:42)
• Re: Full statement logging problematic on larger machines? Guillaume Smet (23:59)

2009-03-12

• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (00:51)
• Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (01:32)
• Re: Full statement logging problematic on larger machines? Tom Lane (01:45)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (02:01)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (02:20)
• Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (02:47)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (03:48)
• Re: Full statement logging problematic on larger machines? Guillaume Smet (07:55)
• Entry point for Postgresql Performance Nagalingam, Karthikeyan (10:52)
• Re: Entry point for Postgresql Performance Ashish Karalkar (11:10)
• Re: Full statement logging problematic on larger machines? Frank Joerdens (13:38)
• Re: Full statement logging problematic on larger machines? Dimitri Fontaine (13:45)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (14:07)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (14:57)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (15:13)
• Re: Proposal of tunable fix for scalability of 8.4 Grzegorz Jaśkiewicz (15:31)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (15:44)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:09)
• Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (17:09)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:39)
• Re: Entry point for Postgresql Performance Rajesh Kumar Mallah (17:41)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:48)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (17:49)
• Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (17:53)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (18:08)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (18:09)
• Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (18:28)
• Re: Proposal of tunable fix for scalability of 8.4 Ron (18:32)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (18:37)
• Re: Proposal of tunable fix for scalability of 8.4 Alvaro Herrera (19:10)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (19:22)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (19:25)
• Re: Proposal of tunable fix for scalability of 8.4 Greg Smith (20:35)
• Re: Full statement logging problematic on larger machines? Laurent Laborde (21:32)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (21:45)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (22:15)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (22:57)

2009-03-13

• Re: Proposal of tunable fix for scalability of 8.4 Robert Haas (01:29)
• Re: Proposal of tunable fix for scalability of 8.4 Greg Smith (03:00)
• Re: Full statement logging problematic on larger machines? sathiya psql (08:28)
• Re: Full statement logging problematic on larger machines? Laurent Laborde (10:21)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (12:38)
• 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (12:44)
• Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (13:05)
• Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (13:28)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (13:36)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (13:43)
• Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (13:54)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (13:57)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (14:56)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Alan Stange (15:20)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (15:55)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (16:18)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (16:42)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (16:54)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Greg Smith (17:15)
• Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (17:16)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (17:21)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (17:23)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:29)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:34)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (17:48)
• Re: Proposal of tunable fix for scalability of 8.4 Kevin Grittner (18:02)
• Re: Proposal of tunable fix for scalability of 8.4 Scott Carey (18:38)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (18:48)
• Re: Proposal of tunable fix for scalability of 8.4 Jignesh K. Shah (20:02)
• Hash Join performance Vamsidhar Thummala (21:15)
• Re: Hash Join performance Tom Lane (21:34)
• Re: Hash Join performance Vamsidhar Thummala (22:11)
• Re: Hash Join performance Tom Lane (23:08)

2009-03-14

• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (01:58)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Tom Lane (02:06)
• Re: Hash Join performance Vamsidhar Thummala (02:10)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Robert Haas (02:37)
• Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4 Gregory Stark (04:02)
• Re: Proposal of tunable fix for scalability of 8.4 david (04:29)
• Re: Proposal of tunable fix for scalability of 8.4 Heikki Linnakangas (08:23)
• Re: Proposal of tunable fix for scalability of 8.4 Simon Riggs (13:30)
• Re: Query much slower when run from postgres function decibel (14:31)
• Re: Query much slower when run from postgres function decibel (14:42)
• Re: Query performance over a large proportion of data decibel (14:47)
• Re: Proposal of tunable fix for scalability of 8.4 decibel (15:06)
• Re: Proposal of tunable fix for scalability of 8.4 decibel (15:22)