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 1tXjnj-00DR0c-9U for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Jan 2025 16:29:59 +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 1tXjnh-001xND-U0 for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Jan 2025 16:29:58 +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 1tXjnh-001xN4-KH for pgsql-hackers@lists.postgresql.org; Tue, 14 Jan 2025 16:29:58 +0000 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tXjng-000NmY-32 for pgsql-hackers@lists.postgresql.org; Tue, 14 Jan 2025 16:29:57 +0000 Received: by mail-il1-x135.google.com with SMTP id e9e14a558f8ab-3a8160382d4so15222115ab.0 for ; Tue, 14 Jan 2025 08:29:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736872196; x=1737476996; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=kwv/uBleTmHnT5k6jAsQWKIgCMP9PE3VVGtCg9nR+F4=; b=Tv+zrl56Y8LaUqTBcWqvGA8wos4GyRyfr9U/s4Mli62LUlEBybmHy5lMFSGrtUvDPM O3oyAf7cOQ+HUhWfbaFZ+mZC8lB31LCRLBpTwkcUVxTRUOZjosiXk/15wc++K5cU1WnU VBvEor5HnD7xU56f1u+8bqzAoSMJKHy2vDxRUuaFXzk7Jrw51eZlMIBnudDBtJYbRdPh 5TqujliLgGE/x7wO2FYP3kE8N1YobKt3BFF/zijq64dLEektk7eFSD7RMMB3Sb9fpCPF jbJWbMxSvFRuFJrYwf028uqq35YHi3/s60J81iEItF6WMZ1b20m7OrQiDt/56xnYb4bX kgQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736872196; x=1737476996; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=kwv/uBleTmHnT5k6jAsQWKIgCMP9PE3VVGtCg9nR+F4=; b=GM9mswvaL/2do9PaOfC3IoN47QjF9fEghI5FOXr2oke5rsypsGcI8qzRv3kqVn5zZe TXdziUOHO7HXlRYHSQHbrjRX/LeK8BPt0TWgk4O2/zGoamgPb0R7mpzOgn7FDHJm6ZNN TF21rwL+mTFKKJ1aRFamZgXNTDxngR11RS92TZMo2H0wYGU8O978ZUgVxTM9KG0dbO7o k99XZboMG66bByN3craIh/3hmFG/2CvQovbweIeLMLATiZ11qdfudQ1RL0d65+U+upIX q/JCxJUleeRJGKgoe+60cvGu1B5BzWHSJTbim7GLQzGDcQu4FxzHlqXm3fkBLBNBGXlu WcKA== X-Forwarded-Encrypted: i=1; AJvYcCVLArZALxvnxfks+4921295FyS5g0QvZEVtIbJ/0bOOjUu/C32dlSL/ynnhorK9q1dg6XuwpfbWTdv2jJy9@lists.postgresql.org X-Gm-Message-State: AOJu0Yys5tjNF4n+8+80plj35ioDVdX77wSEELbl2WHjveJoEEjzeYqa 3m0ww50COXqc/DBnp8XXhv5EP1a7pz7K1X1rlVi9m1HU6c+S/a86OtaVow== X-Gm-Gg: ASbGncuDBm8UxjigV+4eak25MFG3ikYfXRMn1/kBXqmkjmvFXRaXvge4hnkt4LK3SuR fPyNN8ThlMg/OMRrZMeKEqeTp7gvVuW5MGWO1C1xLlVxMryaX+7JlvZUclfBUyMRL0ae7y7t3lo VC4Hu651ol9e/vWd0DGTENSDOHNH6tcbj9iGXR7UT4xfjms2JMYPOj72db0jMKhtux2YBtRytXm +CFGXyXWX7Ln60lykWLlGOEZPNW2oeyDaSp9J7k8DbAa2zWoEv1YwUF20mkLrv+sdakeFo3Fspa WwB2RorxmkPj84fA0qLWSipzLCBYFhOp7D5ELWeLyNwsB/g= X-Google-Smtp-Source: AGHT+IFwRFi0k5AqDmlE/vLvWo+pZEYRZub1XLT1haQgdxts8oKaXqgq9fEfi7uWTpNcO1Q/l5IIoA== X-Received: by 2002:a92:cda3:0:b0:3cd:d02b:d1f3 with SMTP id e9e14a558f8ab-3ce3aa5af2fmr171998695ab.17.1736872195786; Tue, 14 Jan 2025 08:29:55 -0800 (PST) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4ea1b717903sm3535894173.84.2025.01.14.08.29.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Jan 2025 08:29:55 -0800 (PST) Date: Tue, 14 Jan 2025 10:29:53 -0600 From: Nathan Bossart To: Tom Lane Cc: Fujii Masao , Andy Fan , pgsql-hackers@lists.postgresql.org Subject: Re: pgbench error: (setshell) of script 0; execution of meta-command failed Message-ID: References: <87msfz5qv2.fsf@163.com> <87ikqn5em7.fsf@163.com> <2422778.1736521065@sss.pgh.pa.us> <2425050.1736522451@sss.pgh.pa.us> <127979.1736622253@sss.pgh.pa.us> <570943.1736808714@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <570943.1736808714@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jan 13, 2025 at 05:51:54PM -0500, Tom Lane wrote: > It's fair to worry about this, but I don't think my testing that would > prove a lot. AFAICS, whether somebody runs into trouble would depend > on many factors like their specific build process and what versions of > which packages they have installed. > > In any case, I think we have a very limited amount of wiggle room. > We definitely cannot change libpq's ABI without provoking howls of > anguish. Fair point. > I have been wondering whether it would help to add something like > this at the end of port/pqsignal.c in the back branches: > > #ifdef FRONTEND > #undef pqsignal > > /* ABI-compatibility wrapper */ > pqsigfunc > pqsignal(int signo, pqsigfunc func) > { > return pqsignal_fe(signo, func); > } > #endif > > (plus or minus an extern or so, but you get the idea). The point of > this is that compiling against old headers and then linking against > newer libpgport.a would still work. It does nothing however for the > reverse scenario of compiling against new headers and then linking > against old libpgport.a. So I haven't persuaded myself that it's > worth the trouble -- but I'm happy to include it if others think > it would help. After sleeping on it, I think I agree that the extra gymnastics aren't worth it to partially fix something that wasn't supported anyway. But I'm not mortally opposed to it if someone feels strongly that it should be included. -- nathan