Thread: Can CREATE TYPE be used to create a synonym?
Eg: CREATE TYPE DATETIME AS (dummy TIMESTAMP); I suspect not (syntax issues w/ input, output, etc). Is there an alternate way to declare a type synonym? -- Dean
"Dean Gibson (DB Administrator)" <postgresql@ultimeth.com> writes:
> CREATE TYPE DATETIME AS (dummy TIMESTAMP);
> I suspect not (syntax issues w/ input, output, etc). Is there an
> alternate way to declare a type synonym?
CREATE DOMAIN would serve a lot better.
regards, tom lane
BTW, bouncing mail sent to your advertised reply address is a good way
to discourage people from ever answering you again.
regards, tom lane
------- Forwarded Message
Return-Path: MAILER-DAEMON
Delivery-Date: Sun Feb 10 21:57:56 2008
Received: from localhost (localhost)by sss.pgh.pa.us (8.14.2/8.14.2) id m1B2vuOP015376;Sun, 10 Feb 2008 21:57:56 -0500
(EST)
Date: Sun, 10 Feb 2008 21:57:56 -0500 (EST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <200802110257.m1B2vuOP015376@sss.pgh.pa.us>
To: <tgl@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;boundary="m1B2vuOP015376.1202698676/sss.pgh.pa.us"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--m1B2vuOP015376.1202698676/sss.pgh.pa.us
The original message was received at Sun, 10 Feb 2008 21:57:54 -0500 (EST)
from tgl@localhost [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<postgresql@ultimeth.com> (reason: 550 <sss.pgh.pa.us[66.207.139.130]>: Client host rejected: Mail to a list member
mustbe sent via the list)
----- Transcript of session follows -----
... while talking to mail.mailpen.net.:
>>> DATA
<<< 550 <sss.pgh.pa.us[66.207.139.130]>: Client host rejected: Mail to a list member must be sent via the list
550 5.1.1 <postgresql@ultimeth.com>... User unknown
<<< 554 Error: no valid recipients
--m1B2vuOP015376.1202698676/sss.pgh.pa.us
Content-Type: message/delivery-status
Reporting-MTA: dns; sss.pgh.pa.us
Received-From-MTA: DNS; localhost
Arrival-Date: Sun, 10 Feb 2008 21:57:54 -0500 (EST)
Final-Recipient: RFC822; postgresql@ultimeth.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; mail.mailpen.net
Diagnostic-Code: SMTP; 550 <sss.pgh.pa.us[66.207.139.130]>: Client host rejected: Mail to a list member must be sent
viathe list
Last-Attempt-Date: Sun, 10 Feb 2008 21:57:56 -0500 (EST)
--m1B2vuOP015376.1202698676/sss.pgh.pa.us
Content-Type: message/rfc822
Return-Path: <tgl@sss.pgh.pa.us>
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id
m1B2vsOP015373;Sun,10 Feb 2008 21:57:54 -0500 (EST)
To: "Dean Gibson (DB Administrator)" <postgresql@ultimeth.com>
cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Can CREATE TYPE be used to create a synonym?
In-reply-to: <47AFA703.5060907@ultimeth.com>
References: <47AFA703.5060907@ultimeth.com>
Comments: In-reply-to "Dean Gibson (DB Administrator)" <postgresql@ultimeth.com>message dated "Sun, 10 Feb 2008
17:38:11-0800"
Date: Sun, 10 Feb 2008 21:57:53 -0500
Message-ID: <15372.1202698673@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
"Dean Gibson (DB Administrator)" <postgresql@ultimeth.com> writes:
> CREATE TYPE DATETIME AS (dummy TIMESTAMP);
> I suspect not (syntax issues w/ input, output, etc). Is there an
> alternate way to declare a type synonym?
CREATE DOMAIN would serve a lot better.
regards, tom lane
--m1B2vuOP015376.1202698676/sss.pgh.pa.us--
------- End of Forwarded Message
I'm open to suggestions. I've been a member of this list for several years, but every time I post here, some scumbag harvests my eMail address from it and I get hundreds of spam (most gets filtered by postfix). I've gone through a half-dozen eMail addresses on this list alone, and it's been a significant discouragement to posting questions, let alone answering other people. I finally came up with the solution below: If mail to my list address doesn't come from one of your list servers (and those seems to change much more often than any other list I belong to), it gets rejected. And boy, does that catch a lot of spam! I'm curious as to why the list server defaults to using a sender's address as the "Reply-to" address, rather than using the list address. That means that, unless the user is careful to "reply all" (or even better, just reply to the list address), any discussion immediately goes private. In fact, I don't understand why the sender's eMail address is visible at all. Yahoo! is one of the stupidest Internet companies on the face of the planet, and they seem to have been able to figure it out, as has most of the free message board software. And yes, I've read http://www.unicom.com/pw/reply-to-harmful.html -- a very long web page that repeats the same fallacious arguments over and over. They had some validity before spam became a problem, but not now. Anyway, this list is not the place for that discussion. I appreciate the support you give to not only me, but the entire mailing list. I've white-listed you, and I'm open to other suggestions. Sincerely, Dean On 2008-02-10 19:11, Tom Lane wrote: > BTW, bouncing mail sent to your advertised reply address is a good way to discourage people from ever answering you again. > > regards, tom lane > > ----- The following addresses had permanent fatal errors ----- > [postgresql.ultimeth.com] > (reason: 550 <sss.pgh.pa.us[66.207.139.130]>: Client host rejected: Mail to a list member must be sent via the list) >
On Feb 11, 2008 5:06 AM, Dean Gibson (DB Administrator) <postgresql@ultimeth.com> wrote: > If mail to my list address doesn't come from one of your list > servers (and those seems to change much more often than any other list I > belong to), it gets rejected. Those must be some *really* long-lived lists. Our mailserver has been mail.postgresql.org for probably 7 or 8 years now. Many moons ago we did use some additional relay servers, but I don't think we've done that for 5+ years. > I'm curious as to why the list server defaults to using a sender's > address as the "Reply-to" address, rather than using the list address. > That means that, unless the user is careful to "reply all" (or even > better, just reply to the list address), any discussion immediately goes > private. Because thats the convention on these lists that people are used to and prefer in general. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company