Re: [HACKERS] [pgsql-advocacy] Linux.conf.au 2003 Report

2003-01-29 Thread Justin Clift
Christopher Kings-Lynne wrote:


We found out all sorts of interesting places that PostgreSQL is being used:
a large Australian Telco, several restaurants in the Perth area, the Debian
inventory system and the Katie revision control system.  It is also being
evaluated for process control analysis at a steel plant.  Maybe we should
chase some people for case studies?


Definitely.  Forgot to mention this before, but my gf (Carol Ioanni 
<[EMAIL PROTECTED]>) is taking the next couple of weeks to 
assist us pretty much "full time" as thankfully she has some spare time 
on her hands for a bit.  :)

She's been pointed towards our urgent need for Case Studies and has 
already begun working with a couple of places to assist them in getting 
them done.  We have a "standard waiver" that places need to sign so 
we're legally in the clear, and a *very* professionally created Case 
Study Worksheet (donated by Sales.Org for the use of all Free / Open 
Source Software projects) that places work through and which gives us a 
very presentable result.

Carol should be a real expert at making Case Studies pretty soon now is 
my guess, as that's all she's going to be doing.  ;-)

If people could ask the places they have contact with, and whom are 
using PostgreSQL in significant ways, if they'd be happy to be a 
reference PostgreSQL Case Study, that would be great.  Some places might 
ask what's in it for them (it's been happening now and again), and 
pretty much we can tangibly say they'll be included in the PostgreSQL 
Advocacy and Marketing site's "Case Studies" section, and we'll be 
making downloadable PDF's of the Case Studies as well so that people can 
distribute them as needed (i.e. to their CIOs/CEOs/CTOs/etc).

For all places that are happy to get involved in this way, please email 
Carol directly and bring her into the conversation so that we can get 
them using the same Case Study Worksheet, get the waiver signed, and 
start grouping and placing the Case Studies appropriately in the Case 
Studies section.

For further background info, the present page views per day of the 
Advocacy and Marketing site from when the new PostgreSQL portal page 
went live (broken into week long groupings) are:

 5/Jan/03: 2203: +++
 6/Jan/03: 3983: +++
 7/Jan/03: 4493: ++
 8/Jan/03: 4889: +
 9/Jan/03: 4364: ++
10/Jan/03: 3513: 
11/Jan/03: 2112: +++

12/Jan/03: 2735: +++
13/Jan/03: 4405: ++
14/Jan/03: 4226: +
15/Jan/03: 3752: ++
16/Jan/03: 3467: 
17/Jan/03: 3808: ++
18/Jan/03: 1932: +

19/Jan/03: 1777: 
20/Jan/03: 3641: +
21/Jan/03: 4025: +++
22/Jan/03: 3643: +
23/Jan/03: 3310: +++
24/Jan/03: 4242: +
25/Jan/03: 2749: +++

26/Jan/03: 2834: +++
27/Jan/03: 4010: +++
28/Jan/03: 4081: 

Not huge, but not bad for the first version of the site either.  Since 
the Advocacy and Marketing site isn't very large, it means the case 
studies added there generally do get looked at.

Regards and best wishes,

Justin Clift

Chris Kings-Lynne


--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster



Re: [HACKERS] [pgsql-advocacy] Linux.conf.au 2003 Report

2003-01-29 Thread Neil Conway
On Wed, 2003-01-29 at 21:49, Christopher Kings-Lynne wrote:
> * IPV6 data types

Looks like this will be in 7.4, in one form or another.

> - The standard table modification tactic (that I also use) or renaming table
> to *_old and creating new one breaks because the primary key of the new
> table is assigned the same name as the PK of the old, causing CREATE TABLE
> to fail.  This is really annoying.  I think that auto-generated names should
> never collide.

Can this be accomplished without making auto-generated names ugly? And
if not, is it worth the trade-off?

> - I suggested that if pg_dump could dump individual schemas, then they could
> move their 'don't backup' tables to another schema, and just dump the other
> one.

FYI, I submitted a patch for this a couple weeks ago (although it hasn't
been applied yet...) -- it should be in 7.4

Cheers,

Neil
-- 
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC




---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly