On Mon, 10 Dec 2018 16:10:23 +
Paolo Lucente wrote:
> Thanks for your input - always very interesting. I sketched a new note
> in the SQL docs basing on the thread so far:
>
> https://github.com/pmacct/pmacct/commit/e4c594a9f10040b53d4523f7edecf455a20a9151
>
> Hope it looks right enough.
Hi Karl,
Thanks for your input - always very interesting. I sketched a new note
in the SQL docs basing on the thread so far:
https://github.com/pmacct/pmacct/commit/e4c594a9f10040b53d4523f7edecf455a20a9151
Hope it looks right enough.
Paolo
On Sun, Dec 09, 2018 at 07:13:34PM -0600, Karl O. P
On Fri, 7 Dec 2018 16:42:31 +
Paolo Lucente wrote:
> You could make the field variable-length - optimizing space and
> avoiding you the try & error of finding the sweet spot size for the
> as path field at the expense of more computing.
I would not expect a Postgres TEXT column, which is var
Hi Fabien,
I guess this is a case where you have visibility, space and computing.
Pick two.
You could decrease the bgp_aspath_radius which will hinder your
visibility in long as paths (if you care about that) saving space and
computing. Drawback is you would not be safe from long as-sets since
