Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tACJL-00EIIn-99 for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Nov 2024 18:05:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tACJI-0081Mg-Et for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Nov 2024 18:05:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tACJI-0081MX-5E for pgsql-hackers@lists.postgresql.org; Sun, 10 Nov 2024 18:05:16 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tACJG-001AJW-5E for pgsql-hackers@lists.postgresql.org; Sun, 10 Nov 2024 18:05:15 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-e290200a560so3641664276.1 for ; Sun, 10 Nov 2024 10:05:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731261913; x=1731866713; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dH8ApnJOvyIjGYhHxyVCbG7dOSBJfUzpu886joAmo1U=; b=HP19JvA+0EgxVb6lyqS0SWACS1yix9IVBueojMmBAGtvZiQHdsDjTp327uVRLcmzuw QpyqqtwRGe+qM8YOFdp/h9TE1yJQI7FAn8810avfF4qi/yTWsUB135s1X3JEr7on98rO Ig4aWRX45yxUhW0P9eOkqVxtM6/zFsat5rBY3Mq8J32osPBRLf1q5gMcKMmH8kcsoCV5 J/yVOnpfFRB4lOfrUgye9UQv4I/C0IzqJ1AJBWski36O0v3AocLS1CNnA4rDdc7/WhpQ iJoLZK5EYe6uzKCo9CpkkSl/YVakpzKKIU9HB26zffSPK8n4J76On1f7XRPI+ahvkl3U oikw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731261913; x=1731866713; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dH8ApnJOvyIjGYhHxyVCbG7dOSBJfUzpu886joAmo1U=; b=SPIc04YV+sDpttTl7pGHTSF1ME2H0zp3mWYFwYgmRY2X3546aGfwowijGuYc4By/9r dWHTahmB8EM2Aj/IgXhbWI8aeDtQ8dq06O9+S8G9A9/7tJzBNB2YeGmdFHZDGw3kvBHL ATBdOv77c/Ki6SPxD6zuSuADv94jRt30Oa0hfRVcCZzd2CATJyIgsme1/5h2d1d6nPry ECtT0VeMkzLHyV4Qvt4IyEM0c8Uclj7V4wNojplNnRaFk67Fgy9DFnQWrIUSZUmAlt1U bzFlJU50K8/iAgDCATp0yus/hrtzEViF/lGYgZ3XBBoXfoFJpOLOeGQxQKONsdJiCLg2 f7kQ== X-Forwarded-Encrypted: i=1; AJvYcCV2RDdfQ3ISyd4V4pR+6s+9ddM51OtpVpGopDIqu3ycfbEVOYcHtO3cg9Lodkfyuk2faGYcVbkAciFHHFZ+@lists.postgresql.org X-Gm-Message-State: AOJu0YxDNFSBZiWzAczc0x4O14tcTmQwEY8JVurmXKErVT1Mj3hWEDhX v9WeylCF0w4AiQAFxuopMtN59PfSaBHavlFD2xUMT3+9zRl9/wqE0OOAOt9q90btttNvz4YvnvT xQxfLElL4LScho4R9Ug56a0pzRqg= X-Google-Smtp-Source: AGHT+IEtEYNvwoxMFiCqd1X6/NHegjzNfQyHFisaP5ctnJcYYyamrnWNsnpVVqx48LmsjV1NPRSoygTk4Da2NhjcrCs= X-Received: by 2002:a05:690c:6309:b0:6e7:e1aa:ba80 with SMTP id 00721157ae682-6eaddd9afafmr94843447b3.18.1731261913196; Sun, 10 Nov 2024 10:05:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Pavel Stehule Date: Sun, 10 Nov 2024 19:04:34 +0100 Message-ID: Subject: Re: proposal: schema variables To: Dmitry Dolgov <9erthalion6@gmail.com> Cc: Laurenz Albe , Erik Rijkers , Michael Paquier , Amit Kapila , DUVAL REMI , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="000000000000596e8a062692d365" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000596e8a062692d365 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ne 10. 11. 2024 v 18:41 odes=C3=ADlatel Dmitry Dolgov <9erthalion6@gmail.co= m> napsal: > > On Sun, Nov 10, 2024 at 05:19:09PM GMT, Pavel Stehule wrote: > > ne 10. 11. 2024 v 16:24 odes=C3=ADlatel Dmitry Dolgov <9erthalion6@gmai= l.com> > > napsal: > > > > > Hi folks, > > > > > > Thanks for continuing this work. As a side note, I would like to > mention > > > how strange the situation in this CF item is. If I understand > correctly, > > > there are two hackers threads discussing the same patch, with recent > > > patches posted in both of them. This is obviously confusing, e.g. the > > > main concern from another thread, about names clashing, wasn't even > > > mentioned in this one. Is it possible to reconcile development in one > > > thread? > > > > > > > This is probably my error. I don't try to organize threads, just I'll t= ry > > to reply in the thread where I got a question. > > It's fine. I just would appreciate some clarity about which patch to > look at. To confirm, the series in this thread contains everything from > the other one, plus some improvements, right? > I don't remember any change that can be visible for users in this thread. Laurens does very precious code review (thank you again) - there are bigger changes in comments, and less changes in code - some parts of code are moved between patches, some lines were redundant and removed, some lines were artefacts of some git work and were cleaned. Some redundant tests were removed. There is no new code. Regards Pavel --000000000000596e8a062692d365 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
ne 10. 11. 2024 v=C2=A018:41 odes=C3= =ADlatel Dmitry Dolgov <9erthal= ion6@gmail.com> napsal:
> On Sun, Nov 10, 2024 at 05:19:09PM GMT, Pavel Stehule w= rote:
> ne 10. 11. 2024 v 16:24 odes=C3=ADlatel Dmitry Dolgov <9erthalion6@gmail.com>= ;
> napsal:
>
> > Hi folks,
> >
> > Thanks for continuing this work. As a side note, I would like to = mention
> > how strange the situation in this CF item is. If I understand cor= rectly,
> > there are two hackers threads discussing the same patch, with rec= ent
> > patches posted in both of them. This is obviously confusing, e.g.= the
> > main concern from another thread, about names clashing, wasn'= t even
> > mentioned in this one. Is it possible to reconcile development in= one
> > thread?
> >
>
> This is probably my error. I don't try to organize threads, just I= 'll try
> to reply in the thread where I got a question.

It's fine. I just would appreciate some clarity about which patch to look at. To confirm, the series in this thread contains everything from
the other one, plus some improvements, right?

I don't remember any change that can be visible for users in thi= s thread.=C2=A0 Laurens does very precious code review (thank you again) - = there are bigger changes in comments, and less changes in code - some parts= of code are moved between patches, some lines were redundant and removed, = some lines were artefacts of some git work and were cleaned. Some redundant= tests were removed. There is no new code.
=C2=A0
R= egards

Pavel
--000000000000596e8a062692d365--