Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] 2003 Report

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>,Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: [HACKERS] 2003 Report
Date: 2003-02-15 00:24:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-advocacypgsql-hackers
Is the event PostgreSQL should use for coverage in
Australia next year?


Christopher Kings-Lynne wrote:
> Report
> --------------------
> The is an international Linux/Open Source event that attracts
> lots of international speakers.  Total conf attendance was around 360, maybe
> even 400 I think.
> Gavin Sherry was speaking at this particular conf, and I attended as a
> hobbyist.
> PostgreSQL got a reasonable amount of attention, particularly since there
> were no representatives from other database products there.
> Some pics of our PostgreSQL BOF and the Perth Bell Tower:
> (Gavin is the beardy looking dude 3rd from the left :)  I'm taking the
> photo.)
> These are the main questions we where asked, or features that were
> requested:
> * Replication, replication, replication!
> - We told them that there are a few solutions, none of them are particularly
> great.  Gavin got all sorts of ideas about log shipping.
> * IPV6 data types
> - Apparently there are some ISPs in some countries that have started to bill
> people for IPV6 bandwidth, and the lack of IPV6 address types is hurting
> them.
> * Collisions in auto-generated names.
> - 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.
> * Problem:  person has large database with 4 or 5 humungous tables that they
> aren't interested in backing up.  However, they want to back up the rest.
> - 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.
> 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?
> Chris Kings-Lynne
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2003-02-15 00:33:33
Subject: plpython trigger code is wrong (Re: Potential bug -- script that drops postgres server)
Previous:From: Bruce MomjianDate: 2003-02-15 00:19:13
Subject: Re: client_encoding directive is ignored in

pgsql-advocacy by date

Next:From: Curt SampsonDate: 2003-02-15 08:36:39
Subject: Re: [HACKERS] More benchmarking of wal_buffers
Previous:From: Tilo SchwarzDate: 2003-02-14 21:55:51
Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy]

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group