Is there any official style guide of PostgreSQL code ? Like the
"google-styleguide"
(http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml) ?
Regards,
--
Daniel Loureiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
random access, lets discarded it". If in 80's the sequential
access has more cost compared with random access (ok, there's not the
SSD case), will be the PostgreSQL in the same design that it have
nowadays ?
--
Daniel Loureiro.
--
Sent via pgsql-hackers mailing list (pgsql-hac
random access, lets discarded it". An quicksort method in
sequential disk its just awful to be thinking in a non SSD world, but
its possible in an SSD.
If in 80's the sequential access has more cost compared with random
access will be the PostgreSQL in the same design that it have nowaday
t PostgreSQL was been developed and optimized for
sequential access. To get full advantage of SSDs its necessary to
rewrite almost the whole project - there are so much code written with
the sequential mechanism in mind.
--
Daniel Loureiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
So I believe this not a so-necessary feature. Ok I known
that I started this discussion (around this weird feature, not the first and
reasonable feature), but was good to instigate others thoughts.
Sds,
--
Daniel Loureiro
2010/11/30 Bruce Momjian
> Daniel Loureiro wrote:
> > > 3.
not an DBA. Just kidding, but
this happens often enough.
is there another option to implement this ? Its possible to be done by
plugins/extension (in a Firefox browser style) ?
Sds,
--
Daniel Loureiro
--
2010/11/30 Andrew Dunstan
>
>
> On 11/30/2010 09:
apply the modify to the right
> table.
So I guess that I have choose the wrong hack to start.
Just for curiosity, why the result of "WHERE" filter (in
SELECT/DELETE/UPDATE) is not put in memory, i.e. an array of ctid, like an
buffer and then executed by SELECT/DELETE/UPDATE at once ?
Greets,
--
Daniel Loureiro
find
the 1 tuple ? Why the LIMIT clause should be used to speedup only SELECT
statements ? if the programmer know the expected number of affected rows why
not use it to speed up DELETE/UPDATE ?
cheers,
--
Daniel Loureiro
http://diffcoder.blogspot.com/
2010/11/30 Jaime Casanova
> On Mon, Nov
new
grammar 3) change the executor to stop after “n” successful iterations. Is
this correct ?
Greets,
--
Daniel Loureiro
--
http://diffcoder.blogspot.com/
