On Thu, Apr 14, 2022 at 06:19:44PM +0300, Achilleas Mantzios wrote:
> What issue/bug tracking is PostgreSQL itself using?
> What continuous build system (CI/CD) is PostgreSQL itself using?
> Any tool that you ppl or the PostgreSQL infrastructure use that
> links people/committers with bugs/issues,
"David G. Johnston" writes:
> ... And if I know something exists
> in the DB and I want details, doing a name-only search followed by \sf
> seems like it would work well enough.
It could work better though. For example,
regression=# \df *backup*
On Fri, Apr 15, 2022 at 3:02 PM Rob Sargent wrote:
> On 4/15/22 15:52, David G. Johnston wrote:
>
>
>
> On Fri, Apr 15, 2022 at 2:30 PM Rob Sargent wrote:
>
>> On 4/15/22 15:18, David G. Johnston wrote:
>>
>> On Fri, Apr 15, 2022 at 2:04 PM Rob Sargent
>> wrote:
>>
>>> but have not found a comb
"David G. Johnston" writes:
> On Fri, Apr 15, 2022 at 2:20 PM Tom Lane wrote:
>> While I've not yet looked at the code, I've got no reason to think
>> this is anything except fragile argument parsing in \df and \sf.
> I'm unsure about the "extra argument ignored" bit but the rest of "not
> found
On 4/15/22 15:52, David G. Johnston wrote:
On Fri, Apr 15, 2022 at 2:30 PM Rob Sargent wrote:
On 4/15/22 15:18, David G. Johnston wrote:
On Fri, Apr 15, 2022 at 2:04 PM Rob Sargent
wrote:
but have not found a combination of name/args for
genome_threshold_mono(te
On Fri, Apr 15, 2022 at 2:30 PM Rob Sargent wrote:
> On 4/15/22 15:18, David G. Johnston wrote:
>
> On Fri, Apr 15, 2022 at 2:04 PM Rob Sargent wrote:
>
>> but have not found a combination of name/args for
>> genome_threshold_mono(text,text,double
>> precision)
>>
>>
> Per the fine documentatio
On 4/15/22 15:18, David G. Johnston wrote:
On Fri, Apr 15, 2022 at 2:04 PM Rob Sargent wrote:
but have not found a combination of name/args for
genome_threshold_mono(text,text,double precision)
Per the fine documentation:
\df[anptwS+] [ pattern [ arg_pattern ... ] ]
So the correct f
On Fri, Apr 15, 2022 at 2:20 PM Tom Lane wrote:
> Rob Sargent writes:
> > I'm about to unleash new versions of the above and related functions
> > (args will change), so a drops are imminent. Any reason to hold off on
> that?
>
> While I've not yet looked at the code, I've got no reason to think
Rob Sargent writes:
> I'm about to unleash new versions of the above and related functions
> (args will change), so a drops are imminent. Any reason to hold off on that?
While I've not yet looked at the code, I've got no reason to think
this is anything except fragile argument parsing in \df and
On Fri, Apr 15, 2022 at 2:04 PM Rob Sargent wrote:
> but have not found a combination of name/args for
> genome_threshold_mono(text,text,double
> precision)
>
>
Per the fine documentation:
\df[anptwS+] [ pattern [ arg_pattern ... ] ]
So the correct formulation is:
\df genome_threshold_mono te
On 4/15/22 14:22, Adrian Klaver wrote:
On 4/15/22 10:14, Tom Lane wrote:
Rob Sargent writes:
The function in question is working but I'm having trouble getting at
it's current definition and the possibility that there are more
v10->v14
issues in this database. The last ERROR: below seems to
On 4/15/22 10:14, Tom Lane wrote:
Rob Sargent writes:
The function in question is working but I'm having trouble getting at
it's current definition and the possibility that there are more v10->v14
issues in this database. The last ERROR: below seems to me "a system
thing"(tm)
Hmm, it looks l
> On Apr 15, 2022, at 11:14 AM, Tom Lane wrote:
>
> Rob Sargent writes:
>> The function in question is working but I'm having trouble getting at
>> it's current definition and the possibility that there are more v10->v14
>> issues in this database. The last ERROR: below seems to me "a sys
Rob Sargent writes:
> The function in question is working but I'm having trouble getting at
> it's current definition and the possibility that there are more v10->v14
> issues in this database. The last ERROR: below seems to me "a system
> thing"(tm)
Hmm, it looks like \df does not cope well
On 4/15/22 9:53 AM, Rob Sargent wrote:
The function in question is working but I'm having trouble getting at
it's current definition and the possibility that there are more v10->v14
issues in this database. The last ERROR: below seems to me "a system
thing"(tm)
barnard=# \df genome_thre
On 4/15/22 9:53 AM, Rob Sargent wrote:
The function in question is working but I'm having trouble getting at
it's current definition and the possibility that there are more v10->v14
issues in this database. The last ERROR: below seems to me "a system
thing"(tm)
barnard=# \df genome_thr
The function in question is working but I'm having trouble getting at
it's current definition and the possibility that there are more v10->v14
issues in this database. The last ERROR: below seems to me "a system
thing"(tm)
barnard=# \df genome_threshold_mono
On 4/15/22 02:11, Sonai muthu raja M wrote:
Dear Team,
Kindly help us to know that can we see the password history to a User
account in PostgreSQL Database. in PostgreSQL Database.
Do you mean when passwords where changed and what the previous values where?
Also by User account do you mean a
Dear Team,
Kindly help us to know that can we see the password history to a User account
in PostgreSQL Database. in PostgreSQL Database.
Please do the needful since the information require for auditing purpose.
Warm regards,
M Sonai Muthu Raja
Managed Delivery Services - DBA Support
M: +919003
Hey Nick,
Thanks! Yep that’s an alternative (together with a uniqueness constraint
and retry mechanism)
I guess what I’m trying to get my head around is whether and why this would
be better than using advisory locks…
Cheers
Perryn
On Thu, 14 Apr 2022 at 10:32 pm, Nick Cleaton wrote:
> On Thu,
20 matches
Mail list logo
