Re: strict aliasing (was: const correctness)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: strict aliasing (was: const correctness)
Дата
Msg-id 24666.1321301941@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: strict aliasing (was: const correctness)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: strict aliasing (was: const correctness)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: strict aliasing (was: const correctness)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> The results were interesting.  While the small overlap between
> samples from the two builds at most levels means that this was
> somewhat unlikely to be just sampling noise, there could have been
> alignment issues that account for some of the differences.  In
> short, the strict aliasing build always beat the other with 4
> clients or fewer (on this 4 core machine), but always lost with more
> than 4 clients.

That is *weird*.

> Also, is there something I should do to deal with the warnings
> before this would be considered a meaningful test?

Dunno ... where were the warnings exactly?  Also, did you run the
regression tests (particularly the parallel version) against the
build?
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: strict aliasing (was: const correctness)