plethora of systems are built around the notion of programs calling
other programs and managing the process' life cycle. The limiting factor
to such architecture tends to be the OS's process control semantics and
API (notoriously weaker or more contrived on non-unix-like OSs), b
be
paying for that fixed RTT overhead for each command.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this mes
d go 'round.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necessarily reflect the opinions a
On 12/03/2020 00:29, Tom Lane wrote:
Virendra Kumar writes:
Can you please back port patch where if a 0 byte packet sent to PG instance
(Health Checks), it starts complaining about invalid startup packet and flood
the log which increases log size considerably if the health checks are every 3
way you'd also be counting in time a given transaction spent
idling, which IME is one of the biggest source of concurrency headaches
if it's holding locks while doing nothing.
If your use case is unaffected by that, that'd be good news for you.
--
Regards
Fabio Ugo Vench
total, but it's an highly inaccurate process.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not ne
OM ..."
It's easier to write "except" one or two columns from all (*) as to
write names of all columns besides one or two.
What do you thin about it?
Best regards
Stano Motycka
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Te
replication
look-aside CTE I suggested earlier).
its changes with all sync replicas as it's implemented in Stolon
https://github.com/sorintlab/stolon/blob/master/doc/syncrepl.md#handling-postgresql-sync-repl-limits-under-such-circumstances
.
Best regards,
Maksim Milyutin
--
On 19/12/2019 12:25, Andrey Borodin wrote:
Hi Fabio!
Thanks for looking into this.
19 дек. 2019 г., в 17:14, Fabio Ugo Venchiarutti
написал(а):
You're hitting the CAP theorem ( https://en.wikipedia.org/wiki/CAP_theorem )
You cannot do it with fewer than 3 nodes, as the moment yo
whenever a failover occurs. That allows for a simpler failover mechanism
as you know they got the latest WAL location.
If you want an off-the shelf solution, nowadays Patroni seems to be all
the rage.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
obviously at the cost you mentioned)
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necessarily re
type pidgeonhole problem could benefit from something like a GUC
setting to electively break standard JSON compatibility, function
arguments or else.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyri
emit your composite type as a JSON object or
array thereof (types and relations are the same thing).
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group.
their
way and documented this spec weirdness as such in their own project when
they could have just went "look into the specification for oddities".
MySQL silently truncated your overflowing string for years without as
much as a warning, by default. In my book that broke specifi
e concatenated 'cd' in
"fld1"? If not, it's working as per specification & documentation.
I can agree that this sounds like one of those idiosyncratic parts of
the ANSI specification that exist only for compatibility with some
ancient practice, but this behaviour
On 21/10/2019 12:10, Avinash Kumar wrote:
On Mon, Oct 21, 2019 at 4:19 PM Fabio Ugo Venchiarutti
mailto:f.venchiaru...@ocado.com>> wrote:
On 21/10/2019 09:52, Luca Ferrari wrote:
> On Sat, Oct 19, 2019 at 7:46 PM Daulat Ram
mailto:daulat@exponential.com>> wro
depending on which
level was compromised.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not nec
some actual queries could provide good insight for what
else might need changing.
Cheers,
Jeff
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice: This email is confidential and may contain copyright material of
members of the Ocado Group. Opin
eir respective affiliates makes any warranties as to the completeness
or accuracy of any of the information contained herein or that this
message or any of its attachments is free of viruses.
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice: Thi
hnique
--
Regards
Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology
--
Notice: This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necessarily reflect the opinions and views o
the future.
9.6 would be best, because it's had more bug-fix releases.
Aren't all important bugfixes backported to every non-EOL affected
majors at once?
Correct me if I'm wrong but I thought that's the reason minors are
released at unison for all majors.
:)
--
e only for top level query.
Regards
Pavel
--
Regards
Fabio Ugo Venchiarutti
Data Services Department
Ocado Technology
--
Notice: This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may no
one has the old WAL file open, as far as I know.
--
Regards
Fabio Ugo Venchiarutti
Data Services Department
Ocado Technology
--
Notice: This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necess
23 matches
Mail list logo
