Re: Schema variables - new implementation for Postgres 15 (typo)

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, dean(dot)a(dot)rasheed(at)gmail(dot)com, joel(at)compiler(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Schema variables - new implementation for Postgres 15 (typo)
Date: 2022-12-15 06:12:59
Message-ID: CAFj8pRAS8Rd3s81kYdR-aJiOO-hfvidSYM+kY_i4EfY=9h2RAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

st 14. 12. 2022 v 6:20 odesílatel Erik Rijkers <er(at)xs4all(dot)nl> napsal:

> Op 14-12-2022 om 05:54 schreef Pavel Stehule:
> > Hi
> >
> > fresh rebase
>
> typo alert:
>
> v20221214-0003-LET-command.patch contains
>
> errmsg("target session varible is of type %s"
>
> ('varible' should be 'variable')
>

should be fixed now

Thank you for check

>
> Erik
>

Attachment Content-Type Size
v20221215-2-0008-regress-tests-for-session-variables.patch text/x-patch 60.4 KB
v20221215-2-0009-this-patch-changes-error-message-column-doesn-t-exis.patch text/x-patch 26.0 KB
v20221215-2-0007-possibility-to-dump-session-variables-by-pg_dump.patch text/x-patch 19.5 KB
v20221215-2-0006-enhancing-psql-for-session-variables.patch text/x-patch 14.1 KB
v20221215-2-0010-documentation.patch text/x-patch 43.7 KB
v20221215-2-0005-DISCARD-VARIABLES-command.patch text/x-patch 3.2 KB
v20221215-2-0004-support-of-LET-command-in-PLpgSQL.patch text/x-patch 11.9 KB
v20221215-2-0003-LET-command.patch text/x-patch 44.9 KB
v20221215-2-0002-session-variables.patch text/x-patch 110.7 KB
v20221215-2-0001-catalog-support-for-session-variables.patch text/x-patch 89.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amul Sul 2022-12-15 06:19:24 Re: Error-safe user functions
Previous Message Michael Paquier 2022-12-15 06:11:45 Re: Use get_call_result_type() more widely