place for newbie postgresql hackers to work

I know this is a big ask, but once its done its done, and we can
all get on
with the job. Not trying to criticize anyone, this is not a flame! Just
asking for a place for newbies to start hacking.

Why not start with Thomas Swan's earlier posting?:

I just got bit by the identifier name is too long and will be truncated
limitation in Postgresql.

AFIAA there is a limit of 64 characters for identifiers (names of
tables, sequences, indexes, etc...)

I had just started to get in the habit of using serial data types until
I made to tables with long names and the automatic sequence names that
were generated conflicted, *ouch* ...

Is there the possibility of a name conflict resolution during the table
creation phase similar to "the name I want to assign is already taken,
so I'll pick a different name..." on the serial data type?

Chris

Christopher Kings-Lynne wrote:

I know this is a big ask, but once its done its done, and we can
all get on
with the job. Not trying to criticize anyone, this is not a flame! Just
asking for a place for newbies to start hacking.

Why not start with Thomas Swan's earlier posting?:

Because first, exactly that would require a good concept and
(at least I expect it to) a fair amount of system catalog
changes - not the best *newbe* starter.

I like the idea though. Let the experienced developers
identify *legwork* TODO items.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

James Buchanan writes:

Could I ask a huge favour of the experienced PostgreSQL hackers to make a
simple page on the postgreSQL.org website listing TODO items that newbie
hackers can get stuck into?

If there were such places then everyone would be working there and soon
there wouldn't be anything left to do there. ;-)

Traditionally, people work on things that they personally like to see
improved. Reading the mailing lists will point out areas that are
currently little maintained, and also things that people often complain
about but which are not easy to fix.

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

Why not start with Thomas Swan's earlier posting?:

Because first, exactly that would require a good concept and
(at least I expect it to) a fair amount of system catalog
changes - not the best *newbe* starter.

I like the idea though. Let the experienced developers
identify *legwork* TODO items.

From what I can see - there are none. It took me months of reading the
PostgreSQL source code before I could muck with it. (And I still just did
it for fun!) Even the 'basic' stuff like psql and pg_dump modifications
require a knowledge of how foreign keys are stored...

Chris

I like the idea though. Let the experienced developers
identify *legwork* TODO items.

From what I can see - there are none. It took me months of reading the
PostgreSQL source code before I could muck with it. (And I still just did
it for fun!) Even the 'basic' stuff like psql and pg_dump modifications
require a knowledge of how foreign keys are stored...

Good point. Many of the trivial changes spin into difficult territory.
We can suggest items if people ask us.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

PostgreSQL Hackers,

I would like to ask, where can newbie hackers (apprentices) be of use in the
pgsql project?

Thanks Bruce for that work you did showing the TCP/IP diagramme, etc... I
did learn something! Now, the task of self learning from there. For the
server, how to learn the format of PGSQL files? How is data stored? How is
it retrieved so darn quickly? How are index files constructed? So much
glorious knowledge to be had. Source code: start with [...................]
C code file and branch out from there. Please fill in the blanks for me? I
need the start to discover for myself. Learning how to fish is better than
being handed a fish.

With Thanks,
James

----- Original Message -----
From: "Bruce Momjian" <pgman@candle.pha.pa.us>
To: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Cc: "Jan Wieck" <JanWieck@yahoo.com>; "James Buchanan"
<jamesb@northnet.com.au>; "PostgreSQL-development"
<pgsql-hackers@postgresql.org>
Sent: Thursday, June 07, 2001 4:14 PM
Subject: Re: [HACKERS] place for newbie postgresql hackers to work

I like the idea though. Let the experienced developers
identify *legwork* TODO items.

From what I can see - there are none. It took me months of reading the
PostgreSQL source code before I could muck with it. (And I still just

did