Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f9Y1H-0002i0-VM for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Apr 2018 15:32:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f9Y1G-0004DW-NO for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Apr 2018 15:32:14 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f9Y1G-0004DM-AJ for pgsql-hackers@lists.postgresql.org; Fri, 20 Apr 2018 15:32:14 +0000 Received: from mail-qt0-x244.google.com ([2607:f8b0:400d:c0d::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f9Y1C-0007Qq-7Q for pgsql-hackers@postgresql.org; Fri, 20 Apr 2018 15:32:13 +0000 Received: by mail-qt0-x244.google.com with SMTP id f16-v6so6349657qth.0 for ; Fri, 20 Apr 2018 08:32:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tqQ0wshU4430tndNLE2F/6WHWOPlIIgPHVn6O8uQFyQ=; b=LzitLhlJqRy9OGhA/FlLDCLrJoeGe66C+jPohHU5wA8xaweYtHQ3VzE3bsQv0iH3BX 4+hdPBVmXwLKiNikW97DTN8s6pK5Gp/hanaY6GN88QSC0pJ8Q12xuYIwNJTrJGBApmVn Uu589fR1arNy4YcEKw7g7ikaIRn2KIxqU9ko1yPkgyQXOCnvAdpV8hQwatVi/eaTFd4u iKnMa+WmmTTK0v1u3SCpLMSteQWtACyyyDjw54XU9ceIV++FjcI084GbTIuXkyGKDDSy JmDBaD0qK02i1MFCfpnidVvdEmKNojyICnN/XZFK9h3wrxkmxUI+sMHjjXSqJaYWdSmL 40cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tqQ0wshU4430tndNLE2F/6WHWOPlIIgPHVn6O8uQFyQ=; b=f4BXQO+ktqUluULYcF7SrS9ESyY9Zyv7n+0n/sTd/Q0cqnkfYY/67o/KkDx56J+qzy f3QVydviXNabmc2W+dhpSJ0nKKjg4YidFkg5nQGolgYxLSsc5hIJdmWC+zaIWVjjp2Rp AMl/mFRdK5J5to7BWxHXPONICfeUnhgvN/BW2oRmWutdhVU5yV3d5b3yKqiWdfqkIgNf EWfkM+nVYymxYKMeBoY5fIJOmYyqBRsYUDdVWaL6QDMfqUwivxX4/D4rLcgCSO7/bpbq Kny69H5Y53zv/zLjDjNWyN8eCWJpTgTlxPUZSk3HN370v8weBtognzGFw4LSM+OGFXDp YADg== X-Gm-Message-State: ALQs6tAa6vTxSJoZkmz+RdurmPqpo/baGWpT3n8dEgdhKDgnwnKPNRN9 zfSDCiiHWN7Vs9JaZ6vNJZgkBYNSb3qIrq2/3/M= X-Google-Smtp-Source: AB8JxZpxmJhmNDzn/D6k8qAIqRWv8dgNsR06Ui9PGmLvRqfearPchFWGM/FqhIHvEDNj7UyQ8zPP77vrMANDRnMzn5Q= X-Received: by 2002:aed:2c81:: with SMTP id g1-v6mr11707727qtd.285.1524238328715; Fri, 20 Apr 2018 08:32:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.46.238 with HTTP; Fri, 20 Apr 2018 08:32:07 -0700 (PDT) In-Reply-To: References: <20180417141410.GA7917@zakirov.localdomain> From: Robert Haas Date: Fri, 20 Apr 2018 11:32:07 -0400 Message-ID: Subject: Re: [HACKERS] proposal: schema variables To: Pavel Stehule Cc: Arthur Zakirov , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Apr 17, 2018 at 12:28 PM, Pavel Stehule wrote: > It true, so there are lot of "unused" attributes for this purpose, but there > is lot of shared attributes, and lot of shared code. Semantically, I see > variables in family of sequences, tables, indexes, views. Now, it shares > code, and I hope in next steps more code can be shared - constraints, > triggers. I dunno, it seems awfully different to me. There's only one "column", right? What code is really shared here? Are constraints and triggers even desirable feature for variables? What would be the use case? I think stuffing this into pg_class is pretty strange. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company