On Fri, 4 Mar 2022 at 14:41, Gilles Darold wrote:
> Hi,
>
>
> When we want to vacuum and/or analyze all tables in a dedicated schema,
> let's say pg_catalog for example, there is no easy way to do that. The
> VACUUM command doesn't allow it so we have to use \gexec or a SQL script
> to do that.
Hi Everyone,
Let me know if anything else is needed on my end
On Fri, 17 Dec 2021 at 10:54, Dinesh Chemuduru
wrote:
>
>
> On Fri, 3 Dec 2021 at 22:04, Zhihong Yu wrote:
>
>>
>>
>> On Fri, Dec 3, 2021 at 3:15 AM Dinesh Chemuduru
>> wrote:
>>
>>
On Fri, 3 Dec 2021 at 22:04, Zhihong Yu wrote:
>
>
> On Fri, Dec 3, 2021 at 3:15 AM Dinesh Chemuduru
> wrote:
>
>> Hi Michael,
>>
>> Attaching the latest patch here(It's the recent patch), and looking for
>> more suggestions/inputs from the team.
>
Hi Michael,
Attaching the latest patch here(It's the recent patch), and looking for
more suggestions/inputs from the team.
On Fri, 3 Dec 2021 at 13:09, Michael Paquier wrote:
> On Wed, Nov 10, 2021 at 01:58:58PM +0530, Dinesh Chemuduru wrote:
> > The proposed statements are m
On Fri, 19 Nov 2021 at 20:19, Gilles Darold wrote:
> Hi all,
>
>
> Now that the security policy is getting stronger, it is not uncommon to
> create users with a password expiration date (VALID UNTIL). The problem
> is that the user is only aware that his password has expired when he can no
>
Thanks for your time Pavel
> On 09-Nov-2021, at 13:32, Pavel Stehule wrote:
>
>
> Hi
>
> po 8. 11. 2021 v 9:57 odesílatel Dinesh Chemuduru
> napsal:
>> Thanks Zhihong/Pavel,
>>
>>> On Mon, 8 Nov 2021 at 10:03, Pavel Stehule wrote:
>>&g
Thanks Zhihong/Pavel,
On Mon, 8 Nov 2021 at 10:03, Pavel Stehule wrote:
>
>
> po 8. 11. 2021 v 5:24 odesílatel Pavel Stehule
> napsal:
>
>>
>>
>> po 8. 11. 2021 v 5:07 odesílatel Pavel Stehule
>> napsal:
>>
>>>
+set_errcurrent_query (const char *query)
You can remove the
Hi Pavel,
On Sun, 7 Nov 2021 at 12:53, Pavel Stehule wrote:
> Hi
>
> pá 5. 11. 2021 v 19:27 odesílatel Dinesh Chemuduru <
> dinesh.ku...@migops.com> napsal:
>
>> Hi Daniel,
>>
>> Thank you for your follow up, and attaching a new patch which addresses
&
Hi Daniel,
Thank you for your follow up, and attaching a new patch which addresses
Pavel's comments.
Let me know If I miss anything here.
On Thu, 4 Nov 2021 at 17:40, Daniel Gustafsson wrote:
> > On 9 Sep 2021, at 08:23, Dinesh Chemuduru
> wrote:
>
> > Let me try to fix th
On Thu, 9 Sept 2021 at 11:07, Pavel Stehule wrote:
> Hi
>
> I tested the last patch, and I think I found unwanted behavior.
>
> The value of PG_SQL_TEXT is not empty only when the error is related to
> the parser stage. When the error is raised in the query evaluation stage,
> then the value is
Hi Pavel,
On Tue, 24 Aug 2021 at 00:19, Pavel Stehule wrote:
> Hi
>
> pá 20. 8. 2021 v 10:24 odesílatel Dinesh Chemuduru <
> dinesh.ku...@migops.com> napsal:
>
>> On Sun, 25 Jul 2021 at 16:34, Pavel Stehule
>> wrote:
>>
>
> please, can you re
On Sun, 25 Jul 2021 at 16:34, Pavel Stehule wrote:
>
>
> ne 25. 7. 2021 v 12:52 odesílatel Dinesh Chemuduru <
> dinesh.ku...@migops.com> napsal:
>
>> On Sat, 17 Jul 2021 at 01:29, Pavel Stehule
>> wrote:
>>
>>> Hi
>>>
>>>
On Sat, 17 Jul 2021 at 01:29, Pavel Stehule wrote:
> Hi
>
> pá 16. 7. 2021 v 21:47 odesílatel Dinesh Chemuduru <
> dinesh.ku...@migops.com> napsal:
>
>> Hi Everyone,
>>
>> We would like to propose the below 2 new plpgsql diagnostic items,
>> relate
Hi Everyone,
We would like to propose the below 2 new plpgsql diagnostic items,
related to parsing. Because, the current diag items are not providing
the useful diagnostics about the dynamic SQL statements.
1. PG_PARSE_SQL_STATEMENT (returns parse failed sql statement)
2.
14 matches
Mail list logo
