Re: A not so good comparison of MVCC implementations

Michael Paquier <[email protected]> Mon, 29 Jan 2018 13:53:38 +0900
Newsgroups gmane.comp.db.postgresql.advocacy
Message-ID <[email protected]>
On Sun, Jan 28, 2018 at 05:07:43PM -0500, Jonathan S. Katz wrote:
>> On Jan 26, 2018, at 7:03 PM, Robert Haas <[email protected]> wrote:
>> 
>> On Fri, Jan 26, 2018 at 2:07 PM, Jonathan S. Katz <[email protected]> wrote:
>>>> Yeah, that's really deceptive.
>>> 
>>> Skimming the paper, it also does not mention which versions of the software
>>> are being used.  Ideally how the DBs were configured on the hardware
>>> would be great to see too, but that may be asking too much.
>> 
>> That's because they didn't use *any* version of PostgreSQL.  They
>> tested something that they claim works *like* PostgreSQL but is
>> actually not the PostgreSQL code.
> 
> To clarify, that comment was based on all the databases they were using,
> not just PostgreSQL.

Their article never uses "configuration", "configure" and has no mention
about what kind of tuning they've done for any systems.
--
Michael
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlpuqNIACgkQnvQgOdby
QH0I1RAAjfZ5phlwu5DaiAXUJ5oDBMrC5WB1AdfytqscvafTr+4OXya1nYrvpnXd
hBxepWjZiItFwf7YDXHm+RN5APvp5AXM656+IVZfVntzy5KbEzdOROrPZTvqa+O2
bzt1/sxAuflDETRYzL7ywBKO9HM/4VCJjtOt6fnymWwQwDYXWvlRrnEHaDm0vcyM
JqkNl3mUf0EoxYgXSHEaUvD9V1P6VCLN3em+K9MUdtMx70DqdSmwMoMEW3Cry9e0
GFP7CjMJAl83gpx6hY7vk+jAlOjYontYY/BmU2RSfQHELmc5dAWQnoeC/hgyzjyK
3wpIpjyPToRU4OYnlGIWgsLCkKezuDYygXsx9ihkvrl/xZzdyS8Uwa9X8pTQLqNu
I7AErcGeEeSNkUCSZ0KMz3XgVkjkYpACOaZ8MnKjHpsCHOvDUE6zls34t3Xz7Z/K
qobjuTjfUWWSh51zqM5Fn/y6BOiivPdwDGSoBCJggDFWsNnaiux7yliFugQ/dA+c
PEbXKowY78xCM45FOTy80j+Truv+r6JVcuW9ubq56q5sU2I6FFk9FkPNffScbU+U
hZJdL1nVQI2Hm7+DbNbWzGSedpk3ae5b+r0+wPcmsd2fE+6NtMz+L7KRY4aU053l
9eHVfxwUDaPjFV3/q2pBX7Bu6ttRVRNm06QSE6IhaU3Yn7Do/Sw=
=DF3l
-----END PGP SIGNATURE-----