Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iomIr-0000Ni-WC for pgsql-docs@arkaria.postgresql.org; Tue, 07 Jan 2020 10:41:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iomIq-0000EU-E7 for pgsql-docs@arkaria.postgresql.org; Tue, 07 Jan 2020 10:41:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iomIq-0000EN-2N for pgsql-docs@lists.postgresql.org; Tue, 07 Jan 2020 10:41:36 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iomIm-0007mQ-Q5 for pgsql-docs@lists.postgresql.org; Tue, 07 Jan 2020 10:41:34 +0000 Received: by mail-wm1-x344.google.com with SMTP id p9so18381882wmc.2 for ; Tue, 07 Jan 2020 02:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=h4N6l+AEOAhx1rbV7IoG/JlNnjnMpxPonVNy4DI8piI=; b=lAc9p8WJjxaC21ZyxTkWxCV/AUteY/MgG3bnyVqan1NfNqCLDHJCBxV1n71er7sFid GA8ucoGqjRPNic4Pjt+fca9ch2usJ3AX+5/7alMyA2orZJ9w2T9Hv+P3up8GGmbh58US heaI2efGgZHw8MSZBGFNRgf2OQABqvJ3emsl479vTVLIZEmeRAI2SpkKYSTOKwIgY7V8 knhyH96j5K9zfdn/MX+uCQflNQL6X8FL4pgsiif08lU19Rd0j2gA6Y2rKCkgOvMxzAqz 3hvvi8c6tHf+leISarD/+BzFtvSo/KOUZejaQ7mpB3bWvx4mpG6ojghN440VIvFgD2Rf 94vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=h4N6l+AEOAhx1rbV7IoG/JlNnjnMpxPonVNy4DI8piI=; b=lg3QYB2/ou3vzWSUispjFWnab12WvZ9XCI+VOwuwAkYH5teKXQ8SXbkxB6OjBhPinb B6sVDhPsN9U2c0LO93/rCUDo4k+GH7//jhCDhhIKwKlONM27Si4UY3vI05mX5eBvTzJ5 1i7iriuW+1w69qxLj0lBTxQEGiKXZdUBxypcDsFalJlOysu+ecWAcgzyJA83oNXz0q0r Fw8gaYcgoD+4nKTdAs17T4ARByAyYctSs+5eyJe8honyQFgg1ElqM6Xr+OyBOzvj2IeI mzjouuBPewq6Yq/KkPGDYdgKNZrjpdsRycPsxiJq61KnW6osesx3qvgqtI6gj/WhEtMS 1Btg== X-Gm-Message-State: APjAAAVAkjM6Qrx/Jdhrzbt7cOZ2Jxh+pTcrKuyPrV+Yaf2RBe9RqZ0T DHItHp5zL/tonZxfJZ8xzvencA== X-Google-Smtp-Source: APXvYqwuSDq6cpA2lN2FpaWT1MUma0KwkoLqPeL+CGgIl1QDlnn4VdAFWinbPUueCw1ONmlzE10q/w== X-Received: by 2002:a1c:7205:: with SMTP id n5mr40678532wmc.9.1578393691246; Tue, 07 Jan 2020 02:41:31 -0800 (PST) Received: from localhost.localdomain ([212.186.219.234]) by smtp.gmail.com with ESMTPSA id s65sm26837516wmf.48.2020.01.07.02.41.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Jan 2020 02:41:31 -0800 (PST) Message-ID: <13f52b5d04f64804096bca4f2467caacdc199137.camel@cybertec.at> Subject: Re: is_nullable column of information_schema.columns table From: Laurenz Albe To: mdemir4527@gmail.com, pgsql-docs@lists.postgresql.org Date: Tue, 07 Jan 2020 11:41:29 +0100 In-Reply-To: <157756439102.1159.4361947883550826524@wrigleys.postgresql.org> References: <157756439102.1159.4361947883550826524@wrigleys.postgresql.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, 2019-12-28 at 20:19 +0000, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/12/infoschema-columns.html > Description: > > is_nullable column of information_schema.columns table does not show correct > values for columns of views. For tables that column shows correct values > whether a column is nullable or not. I think the documentation should > include this information although better solution is to correct that error. All columns of a view are defined as nullable, whether they can assume that value or not. PostgreSQL does not attempt to deduce the nullability of columns from the view definition. So the information in information_schema.columns is correct. Remember that nullability does not imply that there are actually NULL values. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com