Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mahWR-0007wM-Gk for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Oct 2021 16:54:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mahWQ-0001aY-D0 for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Oct 2021 16:54:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mahWQ-0001aQ-5G for pgsql-hackers@lists.postgresql.org; Wed, 13 Oct 2021 16:54:30 +0000 Received: from mail-io1-xd29.google.com ([2607:f8b0:4864:20::d29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mahWO-00024s-3b for pgsql-hackers@postgresql.org; Wed, 13 Oct 2021 16:54:29 +0000 Received: by mail-io1-xd29.google.com with SMTP id q205so442370iod.8 for ; Wed, 13 Oct 2021 09:54:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=4Ip5mLAwS556wVtnjcXof1KK5rE40Nj6zSey0G96F8E=; b=Vw1hseFUz01PTqxpo6pkvuLCVDZsPFVOpN98FI0Ax9jNGjHudR5/ABNwl30j8LsT+Z o/Ie8crbacNsVSC2UrHZ/d44k0EfUNMAmmgoBFVD+R5i9i7uLlWNjc/2qD27vPF1gV2w 8db43HP7WfDvPlZCIvBpRI+V0yd5lGanU9GjuHETImUilJG3C/qCMQ/bORxiNvaQwrcK crLLEbQ/lf5Mqy9qz9Jx0tPnd80lVuPe7BOBTsB9ddS/iqkXfYCsSuLKbH3epHAbJ4vn ifSS8fwWIWdl2GIx2q325XdFWJL+1oYJoVLkVa0WwXPjd/Y42jXXRyVrCfy4bZsz8q8S CASA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=4Ip5mLAwS556wVtnjcXof1KK5rE40Nj6zSey0G96F8E=; b=LPPbCXLM5rXl6O1zqYK0OxVB1fH9I2A3YN+K/cz5FnIyt0Bp7UANZg4Ho93xAXFzeT XCKLshRqvUkYRgFjAGJrR4pGH+2aXjmLIBlOtZ7B/kRUwLcqfiClaA0RZvUY/bWc2/HC R0eDPNDSwPigbdZ1OIa5BvyZgkH0L5SOoXqTdw44L8jxrRk206iJgOr5cKiR6GaO+6NI 0IGENRhMYlXfZT1frsutl8K2mrHl7RYyrBPrSKxb6RUvxrvl8F9SR29J9jTft3LfWXED cthns/LrmSxwunvXnKQcdpqNg9k1JwhgMOYOP3utuEJO+F4QRok770f69Of+q9PhVB4w vaTg== X-Gm-Message-State: AOAM5326KH773YoxBM0R2FWszwOazn/vyDe6wRAedNb7/UkvGEQewnfw P79pQdgsnuULujzBRs1ol+LkKA== X-Google-Smtp-Source: ABdhPJzV1Mg1WESY3/NnRNcwmBu8emtDAM7wr3sey9Jq6T76mULsiKXj0/qFgRUvo4vn7R/L8ZYBLA== X-Received: by 2002:a05:6638:134f:: with SMTP id u15mr321452jad.145.1634144067450; Wed, 13 Oct 2021 09:54:27 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id g1sm23246ild.86.2021.10.13.09.54.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Oct 2021 09:54:27 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 42F88800837; Wed, 13 Oct 2021 11:54:26 -0500 (CDT) Date: Wed, 13 Oct 2021 11:54:26 -0500 From: Justin Pryzby To: Robert Haas Cc: Stephen Frost , Tom Lane , Peter Geoghegan , Mark Dilger , pgsql-hackers@postgresql.org Subject: Re: pg14 psql broke \d datname.nspname.relname Message-ID: <20211013165426.GD27491@telsasoft.com> References: <22E8AB10-FEB4-40BB-8CAF-16AC9EBA15A3@enterprisedb.com> <529470.1633996189@sss.pgh.pa.us> <573388.1634049057@sss.pgh.pa.us> <20211012151955.GI20998@tamriel.snowman.net> <20211012165745.GM27491@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 13, 2021 at 12:46:27PM -0400, Robert Haas wrote: > On Tue, Oct 12, 2021 at 12:57 PM Justin Pryzby wrote: > > I would prefer if it errored if the datname didn't match the current database. > > After all, it would've helped me to avoid making a confusing problem report. > > How would you have felt if it had said something like: > > error: argument to \d should be of the form > [schema-name-pattern.]relation-name-pattern > > Would that have been better or worse for you than accepting a third > part of the pattern as a database name if and only if it matched the > current database name exactly? I don't normally type \d a.b.c. I think I copied it out of a log message and pasted it, and didn't even really know or expect it to work without removing the datname prefix. After it worked, I noticed a short while later when using the pg14 client that it had stopped working. It seems unfortunate if names from log messages qualified with datname were now rejected. Like this one: | automatic analyze of table "ts.child.cdrs_2021_10_12"... -- Justin