gerry gan writes:
> Thanks for the comments! I have a naive question related to the use of
> advisory lock. Based on my current reasoning about our scenario, consistent
> ordering of commands in two transactions might not help to solve the
> deadlock situation. If advisory lock is used, it can ret
Hi,
Thanks for the comments! I have a naive question related to the use of
advisory lock. Based on my current reasoning about our scenario, consistent
ordering of commands in two transactions might not help to solve the
deadlock situation. If advisory lock is used, it can return false in case
it c
> On Jun 1, 2021, at 3:23 PM, Thomas Munro wrote:
>
> On Wed, Jun 2, 2021 at 7:15 AM Vijaykumar Jain
> wrote:
>> i only get workers to create mv, but refresh mv plan does not use workers
>> for the same conf params.
>
> Yeah, this changed in v14:
>
> https://git.postgresql.org/gitweb/?p=po
On Tue, 2021-06-01 at 20:09 +, Laura Smith wrote:
> I'm creating a Postgres backend for an internal tool which is essentially a
> very simple implementation of multi-lingual CMS.
>
> I am especially interested in feedback and suggestions in relation to the
> following questions:
>
> (a) Is
On Tue, 2021-06-01 at 23:08 +, Laura Smith wrote:
> I didn't consider hstore, I did consider jsonb though.
>
> The thing that made me lean towards individual rows rather than consolidated
> was
> that I thought versioning would ultimately be easier/cleaner to achieve with
> individual rows
On Wednesday, 2 June 2021 00:42, Rob Sargent wrote:
> On 6/1/21 5:00 PM, Laura Smith wrote:
>
> > > What is your notion of "object". I first assumed it was akin to
> > > "document" but then pages have objects.
> >
> > I think my terminology is a bit off.
> >
> > A document/page has object(s) on
