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 1sJce3-005ukG-P9 for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 17:29:23 +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 1sJce1-00HBms-Gb for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 17:29:22 +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 1sJce0-00HBlD-Uo for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 17:29:21 +0000 Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJcdy-001wtK-Sk for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 17:29:20 +0000 Received: by mail-io1-xd31.google.com with SMTP id ca18e2360f4ac-7ea7bcc72caso220472039f.0 for ; Tue, 18 Jun 2024 10:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail-com.20230601.gappssmtp.com; s=20230601; t=1718731758; x=1719336558; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=12Rt9M//rca5HzLTBNJZFyzfYjx2Ho5vJFctLmNAW6s=; b=DDOMiJY1kKTu0r3YemDdNCD4+ASpG8eNR4VInNd760AFr78GfHyZIZVXSbYSsiCFDc HbHecNTBsCTZLSCtBoFs/OTQP0uZdG6nNh1LIBE1XpgqcL0dK8H25JAut7GRkuk/bIk5 1FMJTjtlhLXinXrjlNYBHGaiiqC6e+jShl6meLrV+aOyAcFG4I+pbSO3Mcx3P0oA+J0e i0FgT8ePn07h8wGanBXpDEpyJH2hqReyRIMo/FB/we9Q6eUpDLejYMTe0hyu0aE9h75I 7IuWm7nTjpN0rDFXeXh5bqMyjpmZ4B9U+fo/OkbMiLFgi80tAOWIxCnLFXIpMOmRTtaH KyIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718731758; x=1719336558; h=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=12Rt9M//rca5HzLTBNJZFyzfYjx2Ho5vJFctLmNAW6s=; b=DgbQpN/0Ghh69xhfjE09FrklBv4Nx2XY/PCb0z1wno16AUxe0VnvbUCDx0EEZTg13f 0ZmxFodFrK0JjoVL9Xfqep4k7Mb1ClzBTrmtix6J/gkb+smQDZop3R1Tjpt2UA+reVcG V5uN/OsXVxXde1V1uwa3pZRi5p8ZlZHNPOJOenCsCoYdGzpV++V2IyYD2OYIFmzjp14t pHbvLj3X6814q467D7PmONQOgMEEU75Da9NfubGgXLT41oagLa/lcsT56fsAvJdVdxzq QMO5Z0GgU6dOVAJFx1xJ/FlZLV7Wyzqr7H4MNrAJfMfIPA3rGR0ogpTBPxP2UVq3vbGz gJyg== X-Gm-Message-State: AOJu0YzVBHadzlTFmEV9MqC+RMlXaKu4GB+zISmZsKTnuxrfHVZ4y6Sk KPDw2bh/Sta1DLmVAyV/hxcqDNSWAFi61ojEDWhFAw56OOPxRIG8NeyXa/3+CTs7aNmCw/L1btc SXUJ3aKuZjYDlhKrZb9vXP22H42Eqqw== X-Google-Smtp-Source: AGHT+IEp0NIqt7ENZTvIhHAmjKUlbKFZAZTkk4rg8ZbsQdsVFrWfJwn07Ywxd/1oWv0fsRilbko5UEPtzzN1v7ntlPU= X-Received: by 2002:a05:6e02:1847:b0:376:1808:f8b1 with SMTP id e9e14a558f8ab-3761d76e120mr3739275ab.30.1718731757749; Tue, 18 Jun 2024 10:29:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Wiwwo Staff Date: Tue, 18 Jun 2024 17:28:41 +0000 Message-ID: Subject: Re: HISTIGNORE in psql To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e290f7061b2d6bd8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e290f7061b2d6bd8 Content-Type: text/plain; charset="UTF-8" Hi Adrian, yes, of course, that is what I meant: being able to tell psql to exclude some patterns from being stored in the .psql_history file On Tue, 18 Jun 2024 at 16:12, Adrian Klaver wrote: > On 6/17/24 23:45, Wiwwo Staff wrote: > > Hi! > > As a big history lover, it would be great to have the HISTIGNORE > > functionality added to psql. > > HISTIGNORE is a BASH feature and psql runs in more then the BASH shell. > > Do you mean you would like a clone of that feature added to psql? > > Also psql uses either readline or libedit so it would need to work with > those. > > > > > Have a great day! > > Wiwwo > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --000000000000e290f7061b2d6bd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Adrian,
yes, of course, that is what I meant= : being able to tell psql to exclude some patterns from being stored in the= .psql_history file

--000000000000e290f7061b2d6bd8--