On Dec 21, 2006, at 9:56 AM, Simon Riggs wrote:
On Thu, 2006-12-21 at 09:36 -0500, Matthew O'Connor wrote:
Richard Huxton wrote:
Simon Riggs wrote:
- improve RI check perf by caching small, static tables in each
backend
- apply index filter conditions on index scan to avoid heap lookup
For
On Thu, 2006-12-21 at 09:36 -0500, Matthew O'Connor wrote:
> Richard Huxton wrote:
> > Simon Riggs wrote:
> >> - improve RI check perf by caching small, static tables in each backend
> >> - apply index filter conditions on index scan to avoid heap lookup
> >
> > For fkey checks against a basically
Richard Huxton wrote:
Simon Riggs wrote:
- improve RI check perf by caching small, static tables in each backend
- apply index filter conditions on index scan to avoid heap lookup
For fkey checks against a basically static table could you get away with
just checking the index and not the tabl
Simon Riggs wrote:
For 8.3 my goal is to improve the performance of single row operations,
Great. That's something that's useful across the board.
Currently, I'm aware of these possibilities, some fairly vague
...
- avoid RI checks for update of a column not mentioned in SET
Linked at lea
For 8.3 my goal is to improve the performance of single row operations,
such as
INSERT INTO foo ... VALUES (...)
UPDATE foo SET WHERE =
DELETE FROM foo WHERE =
OLTP Assumptions
- all statements are prepared first, then executed with bound
parameters.
- need to