From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v4 2/2] box: introduce _vsession_settings sysview
Date: Wed, 27 Nov 2019 13:34:32 +0300 [thread overview]
Message-ID: <CAPZPwLqSv8=H_tv+Yakh=Dai-n0K6KfKErXa2E3S+9uTAEdgtA@mail.gmail.com> (raw)
In-Reply-To: <20191127051523.qm3mjvng4pnqoe4y@tarantool.org>
Pragmas are of course a dead end, but pragmas themselves are
unimportant, so it's still unclear why one should bother about them,
as opposed to, for example, caring about foreign key checks for all
front ends.
But fine, assuming one wants to remove prgamas, adding extra overhead
to session management is a bad idea. One could have a global sysview
_vsettings with all the settings, perhaps even ones from box.cfg, and
that would be enough.
next prev parent reply other threads:[~2019-11-27 10:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 12:11 [Tarantool-patches] [PATCH v4 0/2] " imeevma
2019-11-23 12:11 ` [Tarantool-patches] [PATCH v4 1/2] sysview: make get() and create_iterator() methods virtual imeevma
2019-11-23 12:12 ` [Tarantool-patches] [PATCH v4 2/2] box: introduce _vsession_settings sysview imeevma
2019-11-24 15:27 ` Vladislav Shpilevoy
2019-11-27 9:53 ` Mergen Imeev
2019-11-27 23:14 ` Vladislav Shpilevoy
2019-11-26 21:12 ` Konstantin Osipov
2019-11-27 5:15 ` Kirill Yukhin
2019-11-27 10:34 ` Konstantin Osipov [this message]
2019-11-27 10:52 ` Mergen Imeev
2019-11-27 11:05 ` Konstantin Osipov
2019-11-27 11:18 ` Mergen Imeev
2019-11-27 11:37 ` Konstantin Osipov
2019-11-27 12:12 ` Mergen Imeev
2019-11-28 8:46 [Tarantool-patches] [PATCH v4 0/2] Introduce " imeevma
2019-11-28 8:46 ` [Tarantool-patches] [PATCH v4 2/2] box: introduce " imeevma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPZPwLqSv8=H_tv+Yakh=Dai-n0K6KfKErXa2E3S+9uTAEdgtA@mail.gmail.com' \
--to=kostja.osipov@gmail.com \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v4 2/2] box: introduce _vsession_settings sysview' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox