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 1rqL5v-00Bpsh-Oj for pgsql-general@arkaria.postgresql.org; Fri, 29 Mar 2024 22:53:08 +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 1rqL5u-005A9f-U3 for pgsql-general@arkaria.postgresql.org; Fri, 29 Mar 2024 22:53:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rqL5u-005A7Z-JO for pgsql-general@lists.postgresql.org; Fri, 29 Mar 2024 22:53:06 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rqL5p-007MUb-HU for pgsql-general@lists.postgresql.org; Fri, 29 Mar 2024 22:53:05 +0000 Received: by mail-pf1-x436.google.com with SMTP id d2e1a72fcca58-6eaf1005fcaso351120b3a.3 for ; Fri, 29 Mar 2024 15:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711752779; x=1712357579; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=IwiUUTeIvPunwjqNnR1KloQQEcCivA08xg89asgjZTk=; b=gThuLImTwiPksqJCqOqe2B9zVViMRHHAZz1crjhTteJkDY00tsv9PRygnYCaFk9bXC 8KoJO0zJ3mhYGzh9p99cviAIoobGPiYk1Uv2iOv1eQ0+Q/tBsjPTk13tVpw1t/thwIdK tLJQj2vToI4PmpMSjEdgHDcPPTfVp/6VJzhUFbQnzgJIuIQVekFvdjx58RCaptGRae5V K2nqb0GZLlHqqauJcXR/5VuVWSj1FyQBY0NOWcK1w11trgYk5WQN24m3HUBYksM4s5KO 7PF23Bu6d6o2pDPPFxISlo3lmvm0MripUHa4P3C/vQ0VbtdAVX4uqteMtcHLqrIhd7oT e5xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711752779; x=1712357579; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IwiUUTeIvPunwjqNnR1KloQQEcCivA08xg89asgjZTk=; b=eiw50znfdGNBQJSSg5YBVRQ4p+Gmhu64JZPK12T6qZfq1xOPWs2oGPnMOu4hHvFBna fraD/gVJJvIIsQoi69CrWA4C63ES4GUhSFG2wNPcDGho5PZsibkTNKlhRwpdy5d+YRMu jkFnbFH2vKoSKrwGvowcHgp/6HZsrl2djyc5iLeyxX+7ahIN2ODYcJ7fMos7/8p8350W 7UGNI9zzZVNdkNeSb/0I2ivL512cRYiHzgi2g5tNVDwIjqNYhhLWx2+uNkoTyM8QAlzJ 5vuPe8ZuYUSeY+6LtR993bhQ4u5hbdLwF5cKu23PAC0/5+2n8vk9PNrmWNXpJnO2Cn9a 2ytA== X-Gm-Message-State: AOJu0YwAI/05tlxcSih1OrOnQ8dKrPv/HH8+60R22e691lbwG0L4dUbE prXn3FHcRBMwLvOAmzlVkFLdCu3FVTMJBn1IYdhFmZWmFrkOUpCbvPl+aaTP X-Google-Smtp-Source: AGHT+IG4PydsDNLdvZFePcKQCD+s1pVIP0pIqZt6GLMRhcsHUTT4BLS5maTrLYaEfijtSbhWgkBWIQ== X-Received: by 2002:a05:6a20:6a1c:b0:1a7:1f8:e046 with SMTP id p28-20020a056a206a1c00b001a701f8e046mr1650460pzk.4.1711752778684; Fri, 29 Mar 2024 15:52:58 -0700 (PDT) Received: from ?IPV6:2601:681:5a00:f790:f50d:5aaa:b366:26d4? ([2601:681:5a00:f790:f50d:5aaa:b366:26d4]) by smtp.gmail.com with ESMTPSA id lx1-20020a17090b4b0100b002a20d5c4ee6sm2341923pjb.3.2024.03.29.15.52.57 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Mar 2024 15:52:58 -0700 (PDT) Message-ID: Date: Fri, 29 Mar 2024 16:52:56 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to reference a DB with a period in its name ? Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/29/24 15:36, David Gauthier wrote: > Ya, I kind of agree on the >1 DB connections not allowed.  It > (perl/DBI) does allow for >1 active DB handles (objects).  But of > course those handles/objects have different names and that's how to > work with the different ones (not a DB prefix like what I have).  > Still, it accepted the name in the syntax if it didn't have a ".".  I > kinda liked the db prefix because I'm doing these sweeping deletes and > I wanted to make extra-sure that I was deleting from the correct DB. > > I'm going to ask them to just create another DB without the "." in the > name.  All the code has the prefix and I don't want to uproot that > (because it's working). Or is it working, really?  Or are you working around it?