Hi,
Le mer. 8 janv. 2025 à 17:41, Mahendra Singh Thalor a
écrit :
> On Wed, 8 Jan 2025 at 20:07, Mahendra Singh Thalor
> wrote:
> >
> > Hi all,
> >
> > On Wed, 8 Jan 2025 at 00:34, Mahendra Singh Thalor
> wrote:
> > >
> > > On Mon, 6 Jan 2025 at 23:05, Nathan Bossart
> wrote:
> > > >
> > > >
Hi,
Le dim. 19 janv. 2025 à 06:40, Sami Imseih a écrit :
> > Hmm. I am reading Tom's opinion that goes toward not going in this
> > direction for more commands, with the point to extend EXPLAIN to show
> > this kind of information:
> > https://www.postgresql.org/message-id/1692530.1736369...@ss
Le lun. 20 janv. 2025 à 04:28, Sami Imseih a écrit :
> > > > Hmm. I am reading Tom's opinion that goes toward not going in this
> > > > direction for more commands, with the point to extend EXPLAIN to show
> > > > this kind of information:
> > > >
> https://www.postgresql.org/message-id/1692530.
Le mer. 8 janv. 2025 à 21:44, Sami Imseih a écrit :
> > I think DEBUG is perfectly appropriate for this sort of message.
>
> I am curious what are the thoughts on introducing a
> CREATE INDEX VERBOSE which can provide this info?
> similar to users scripting VACUUM VERBOSE to log
> more details ab
Le mer. 8 janv. 2025 à 21:35, Tom Lane a écrit :
> Guillaume Lelarge writes:
> > I tend to agree it might be better than Benoit's patch on the index
> > messages, though I'm afraid that DEBUG1 level won't work for many users.
> > DEBUGx are for developers,
ng temp files but if this isn't doable easily or without
mistakes, then don't log the query at all.
--
Guillaume Lelarge
Consultant
https://dalibo.com
QUERY PLAN
-
Seq Scan on t1 (actual time=0.009..0.067 rows=1.00 loops=1)
Filter: (id < 2)
Rows Removed by Filter: 999
Buffers: shared hit=5
Planning:
Buffers: shared hit=5
Planning Time: 0.070 ms
Execution Ti
On 04/02/2025 19:14, Guillaume Lelarge wrote:
On 04/02/2025 17:59, Tom Lane wrote:
Guillaume Lelarge writes:
v2 is attached.
This seems pretty much entirely useless to me. The password
has already been leaked to the log (*and* the network, if
session is unencrypted), so what's the poi
d).
I'm obviously +1 on this patch since I sent kinda the same patch two
weeks ago
(https://www.postgresql.org/message-id/8f17493f-0886-406d-8573-0fadcb998b1d%40dalibo.co).
The only major difference is that your patch can completely disable
plain text passwords. More options, that sounds better to me.
--
Guillaume Lelarge
Consultant
https://dalibo.com
On 22/02/2025 09:07, Guillaume Lelarge wrote:
On 21/02/2025 23:33, Greg Sabino Mullane wrote:
There have been a few complaints lately about the fact that we
cavalierly allow clear text passwords to be sent when doing CREATE
USER or ALTER USER. These, of course, can end up in many places, such
On 24/02/2025 14:55, Greg Sabino Mullane wrote:
Guillaume Lelarge <mailto:guillaume.lela...@dalibo.com>> wrote:
I'm obviously +1 on this patch since I sent kinda the same patch two
weeks ago
Ha ha, my brain forgot about that one (even though I commented on it!) -
apol
&startup_data, &startup_data_len);
+ /* Calculate total fork duration in child backend for logging */
+ if (child_type == B_BACKEND)
+ {
+ INSTR_TIME_SET_CURRENT(conn_timing.fork_duration);
+ INSTR_TIME_SUBTRACT(conn_timing.fork_duration,
+
101 - 112 of 112 matches
Mail list logo
