pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Claus Guttesen <kometen@gmail.com>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Estimate the size of the SQL file generated by pg_dump utility
Date: Tue, 6 Mar 2007 16:09:15 +0100
Message-ID: <b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com> (raw)
In-Reply-To: <45ED83C1.6000003@modgraph-usa.com>
References: <45ECCFCA.2010501@presinet.com>
	<200703060222.l262MLi09584@momjian.us>
	<20070306084437.1f52c123.wmoran@collaborativefusion.com>
	<45ED83C1.6000003@modgraph-usa.com>

> > I'm curious, what problem does the disclaimer cause?
> >
> > I wrote the following TOS for my personal system:
> > https://www.potentialtech.com/cms/node/9
> > Excerpt of the relevant part:
> > I have no idea if that's legally binding or not, but I've talked to a few
> > associates who have some experience in law, and they all argue that email
> > disclaimers probably aren't legally binding anyway -- so the result is
> > undefined.
>
> No, it's not legally binding.  Agreements are only binding if both parties agree, and someone sending you email has not consented to your statement.  If I send you something with a copyright mark, you'd better respect it unless you have a signed agreement granting you rights.  Federal law always wins.
>
> Disclaimers are bad for two reasons.  First, they're powerless.  Just because Acme Corp. attaches a disclaimer doesn't mean they've absolved themselves of responsibility for the actions of their employees.  Second, they're insulting to the employees.  It's a big red flag saying, "We, Acme Corp., hire clowns we don't trust, and THIS person may be one of them!"

Dear sirs, this is off-topic at best. Pls. discontinue this thread.

regards
Claus



view thread (10+ messages)  latest in thread

Message-ID: <b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com>
Permalink:  ../b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com/
Also on:    postgresql.org/message-id/b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: kometen@gmail.com, cjames@modgraph-usa.com, wmoran@collaborativefusion.com
  Subject: Re: Estimate the size of the SQL file generated by pg_dump utility
  In-Reply-To: <b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com>
  References: <45ECCFCA.2010501@presinet.com> <200703060222.l262MLi09584@momjian.us> <20070306084437.1f52c123.wmoran@collaborativefusion.com> <45ED83C1.6000003@modgraph-usa.com> <b41c75520703060709j23a17106h184a173f6bcb6b49@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox