Thread: Good Books
Hi I am new to PostgreSQL and find that the standard documentation is very thin. I would like to buy a more comprehensive book. All the available books seem very out of date!!! Firstly, does it matter if I buy a book that was published in Feb 2003? Will such a book be hopelessly out of date? Does anyone know of any books that will be releasing imminently? Thanks Craig
On Thu, Mar 24, 2005 at 14:37:59 +0200, postgresql@bryden.co.za wrote: > Hi > > I am new to PostgreSQL and find that the standard documentation is very > thin. I would like to buy a more comprehensive book. All the available > books seem very out of date!!! Firstly, does it matter if I buy a book > that was published in Feb 2003? Will such a book be hopelessly out of > date? What parts of the documentation do you find thin? Without knowing what you need extra info on, it will be hard to recommend other documentation.
On Thu, 2005-03-24 at 06:37, postgresql@bryden.co.za wrote: > Hi > > I am new to PostgreSQL and find that the standard documentation is very > thin. I would like to buy a more comprehensive book. All the available > books seem very out of date!!! Firstly, does it matter if I buy a book > that was published in Feb 2003? Will such a book be hopelessly out of > date? > > Does anyone know of any books that will be releasing imminently? The first books to pick up and become familiar with are the ones on database theory, not specifically postgresql. While a lot of other databases come with documentation that explains a lot of relational theory, PostgreSQL comes with documentation that pretty much assumes you already understand database basics and are looking for how to do some particular thing in postgresql. So it's not that it's thin in terms of covering PostgreSQL, but thin in terms that it's focus is not general database theory, but postgresql specifics. A lot of the books written about PostgreSQL have more information about theory, but honestly, a good generic database oriented book is usually more helpful at first for most folks. If you're already familiar with basic db theory, then look for some of the pgsql books that have been placed online by their publishers.
postgresql@bryden.co.za wrote: > I am new to PostgreSQL and find that the standard documentation is > very thin. It's about 1200 pages, which is thicker than any other book you will find. Certainly, some books cover specific topics in more depth or different style, but you need to decide which topics you would be interested in. > I would like to buy a more comprehensive book. I think that is impossible. You can get more specialized or in-depth books, but not more comprehensive ones. > All the > available books seem very out of date!!! Firstly, does it matter if I > buy a book that was published in Feb 2003? Will such a book be > hopelessly out of date? That, too, depends on the topic. -- Peter Eisentraut http://developer.postgresql.org/~petere/
Hi Bruno There are a lot of the topics that I feel could have better (or more comprehensive examples). In particular I am thinking of plpgsql. One example is information about working with Exceptions (postgresql specific) and another is the small amount of info about the RAISE Statement. Refering to my mention of exceptions above, the following is information that I could not find in the standard docs: How to use(Return using RAISE) the actual exception code and message once you have handled the error. This is especially usefull if you have used WHEN OTHERS to catch the error. Thanks Craig > On Thu, Mar 24, 2005 at 14:37:59 +0200, > postgresql@bryden.co.za wrote: >> Hi >> >> I am new to PostgreSQL and find that the standard documentation is very >> thin. I would like to buy a more comprehensive book. All the available >> books seem very out of date!!! Firstly, does it matter if I buy a book >> that was published in Feb 2003? Will such a book be hopelessly out of >> date? > > What parts of the documentation do you find thin? Without knowing what > you need extra info on, it will be hard to recommend other documentation. > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq >
On Thu, Mar 24, 2005 at 03:41:06PM +0200, postgresql@bryden.co.za wrote: Craig, > There are a lot of the topics that I feel could have better (or more > comprehensive examples). In particular I am thinking of plpgsql. One > example is information about working with Exceptions (postgresql specific) > and another is the small amount of info about the RAISE Statement. > > Refering to my mention of exceptions above, the following is information > that I could not find in the standard docs: > How to use(Return using RAISE) the actual exception code and message once > you have handled the error. This is especially usefull if you have used > WHEN OTHERS to catch the error. No book will tell you how to do that, because the EXCEPTION support in plpgsql is new as of Postgres 8.0, and some things are not there yet. If the documentation doesn't say how to do it, then maybe there is no way. You'd need to convince a hacker that it's a useful feature so they can add it. -- Alvaro Herrera (<alvherre[@]dcc.uchile.cl>) "I personally became interested in Linux while I was dating an English major who wouldn't know an operating system if it walked up and bit him." (Val Henson)
On Thu, 2005-03-24 at 08:41, postgresql@bryden.co.za wrote:
> Hi Bruno
>
> There are a lot of the topics that I feel could have better (or more
> comprehensive examples). In particular I am thinking of plpgsql. One
> example is information about working with Exceptions (postgresql specific)
> and another is the small amount of info about the RAISE Statement.
>
> Refering to my mention of exceptions above, the following is information
> that I could not find in the standard docs:
> How to use(Return using RAISE) the actual exception code and message once
> you have handled the error. This is especially usefull if you have used
> WHEN OTHERS to catch the error.
>
To be honest, you're not going to find any books covering that because
the code is just too new to have been in the pipeline for any of the
books currently in print. The only one I can think of that might have
something is Korry Douglas's PostgreSQl 2nd Edition that I have heard
has some expanded information on plpgsql, though I haven't read it so I
can't verify that for you (read that as don't buy that book based on the
above... but see if you can find it and verify the above).
I think the only other book that is soon to be out is Begining Databases
with PostgreSQL book from Apress, but I know it doesn't have that deep a
level of what your looking for on that topic. Of the other books I know
about in the works... some of them could include that kind of info
maybe, but they wont be out till summer at the earliest and more likely
the end of the year.
Of course this assumes you can do it at all ;-)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
If you are looking for a database theory book, I highly recommend "An
Introduction to Database Systems" by C.J. Date. It's very theoretical,
but it's precisely worded and very interesting.
Regards,
Jeff Davis
On Thu, 2005-03-24 at 06:54 -0600, Scott Marlowe wrote:
> On Thu, 2005-03-24 at 06:37, postgresql@bryden.co.za wrote:
> > Hi
> >
> > I am new to PostgreSQL and find that the standard documentation is very
> > thin. I would like to buy a more comprehensive book. All the available
> > books seem very out of date!!! Firstly, does it matter if I buy a book
> > that was published in Feb 2003? Will such a book be hopelessly out of
> > date?
> >
> > Does anyone know of any books that will be releasing imminently?
>
> The first books to pick up and become familiar with are the ones on
> database theory, not specifically postgresql. While a lot of other
> databases come with documentation that explains a lot of relational
> theory, PostgreSQL comes with documentation that pretty much assumes you
> already understand database basics and are looking for how to do some
> particular thing in postgresql. So it's not that it's thin in terms of
> covering PostgreSQL, but thin in terms that it's focus is not general
> database theory, but postgresql specifics.
>
> A lot of the books written about PostgreSQL have more information about
> theory, but honestly, a good generic database oriented book is usually
> more helpful at first for most folks.
>
> If you're already familiar with basic db theory, then look for some of
> the pgsql books that have been placed online by their publishers.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
Robert Treat <xzilla@users.sourceforge.net> writes:
> On Thu, 2005-03-24 at 08:41, postgresql@bryden.co.za wrote:
>> Refering to my mention of exceptions above, the following is information
>> that I could not find in the standard docs:
>> How to use(Return using RAISE) the actual exception code and message once
>> you have handled the error. This is especially usefull if you have used
>> WHEN OTHERS to catch the error.
> Of course this assumes you can do it at all ;-)
Which you can't. That isn't a documentation shortcoming, it's an
implementation shortcoming ...
regards, tom lane
There's actually a list of recommended books up on techdocs: http://techdocs.postgresql.org/#books It could use a little updating, but is still pretty good. Robert Treat On Thu, 2005-03-24 at 09:57, Jeff Davis wrote: > If you are looking for a database theory book, I highly recommend "An > Introduction to Database Systems" by C.J. Date. It's very theoretical, > but it's precisely worded and very interesting. > > Regards, > Jeff Davis > > > On Thu, 2005-03-24 at 06:54 -0600, Scott Marlowe wrote: > > On Thu, 2005-03-24 at 06:37, postgresql@bryden.co.za wrote: > > > Hi > > > > > > I am new to PostgreSQL and find that the standard documentation is very > > > thin. I would like to buy a more comprehensive book. All the available > > > books seem very out of date!!! Firstly, does it matter if I buy a book > > > that was published in Feb 2003? Will such a book be hopelessly out of > > > date? > > > > > > Does anyone know of any books that will be releasing imminently? > > > > The first books to pick up and become familiar with are the ones on > > database theory, not specifically postgresql. While a lot of other > > databases come with documentation that explains a lot of relational > > theory, PostgreSQL comes with documentation that pretty much assumes you > > already understand database basics and are looking for how to do some > > particular thing in postgresql. So it's not that it's thin in terms of > > covering PostgreSQL, but thin in terms that it's focus is not general > > database theory, but postgresql specifics. > > > > A lot of the books written about PostgreSQL have more information about > > theory, but honestly, a good generic database oriented book is usually > > more helpful at first for most folks. > > > > If you're already familiar with basic db theory, then look for some of > > the pgsql books that have been placed online by their publishers. > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 9: the planner will ignore your desire to choose an index scan if your > > joining column's datatypes do not match > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
"...and very interesting."
The Date book should be required reading in computer science 101, but "very
interesting" implies that your only other hobby is watching grass grow.
Rick
Jeff Davis
<jdavis-pgsql@empires.o To: Scott Marlowe <smarlowe@g2switchworks.com>
rg> cc: postgresql@bryden.co.za, PgSQL General List
<pgsql-general@postgresql.org>
Sent by: Subject: Re: [GENERAL] Good Books
pgsql-general-owner@pos
tgresql.org
03/24/2005 09:57 AM
If you are looking for a database theory book, I highly recommend "An
Introduction to Database Systems" by C.J. Date. It's very theoretical,
but it's precisely worded and very interesting.
Regards,
Jeff Davis
On Thu, 2005-03-24 at 06:54 -0600, Scott Marlowe wrote:
> On Thu, 2005-03-24 at 06:37, postgresql@bryden.co.za wrote:
> > Hi
> >
> > I am new to PostgreSQL and find that the standard documentation is very
> > thin. I would like to buy a more comprehensive book. All the available
> > books seem very out of date!!! Firstly, does it matter if I buy a book
> > that was published in Feb 2003? Will such a book be hopelessly out of
> > date?
> >
> > Does anyone know of any books that will be releasing imminently?
>
> The first books to pick up and become familiar with are the ones on
> database theory, not specifically postgresql. While a lot of other
> databases come with documentation that explains a lot of relational
> theory, PostgreSQL comes with documentation that pretty much assumes you
> already understand database basics and are looking for how to do some
> particular thing in postgresql. So it's not that it's thin in terms of
> covering PostgreSQL, but thin in terms that it's focus is not general
> database theory, but postgresql specifics.
>
> A lot of the books written about PostgreSQL have more information about
> theory, but honestly, a good generic database oriented book is usually
> more helpful at first for most folks.
>
> If you're already familiar with basic db theory, then look for some of
> the pgsql books that have been placed online by their publishers.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
your
> joining column's datatypes do not match
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Thursday 24 March 2005 4:37 am, postgresql@bryden.co.za wrote: > Hi > > I am new to PostgreSQL and find that the standard documentation is > very thin. I would like to buy a more comprehensive book. Funny. I just downloaded and printed the comprehensive manual available at: http://www.postgresql.org/docs/manuals/ At 1422 US letter pages printed double-sided it ended up being over 3" or about 8cm thick. And it's available in commented and non-commented on-line versions as well. Although there is always room for improvement, I have not personally encountered any other open-source project with such comprehensive documentation. What specific information are you seeking. Maybe someone can point you in the right direction. Cheers, Steve
On Thu, 2005-03-24 at 10:59 -0500, Richard_D_Levine@raytheon.com wrote:
> "...and very interesting."
>
> The Date book should be required reading in computer science 101, but "very
> interesting" implies that your only other hobby is watching grass grow.
>
> Rick
[ referring to "An Introduction to Database Systems" by CJ Date ]
Hah. I'm sure there are many that would find it boring, but I find it
much more readable than, say, the Knuth books. It's all relative, I
suppose. I found it interesting because at the time I was reading it it
helped me solve some practical problems I was having without resorting
to kludges and client-side programming.
Regards,
Jeff Davis
PostgreSQL 8.0.0beta5 Documentation
Chapter 35.9 bottom of the page.
"RAISE EXCEPTION presently always generates the same SQLSTATE code,
P0001, no matter what message it is invoked with. It is possible
to trap this exception with EXCEPTION ... WHEN RAISE_EXCEPTION THEN ...
but there is no way to tell one RAISE from another. "
It would seem a kludge would be to set a variable at each point of possible
failure, such as continuously incrementing a variable as it goes through the
code. You would then be able to use a standard case statement or call an
error message function to return a meaningful error message.
In any case, the documentation very clearly says you can't do it.
<postgresql@bryden.co.za> wrote in message
news:43109.127.0.0.1.1111671666.squirrel@127.0.0.1...
> Hi Bruno
>
> There are a lot of the topics that I feel could have better (or more
> comprehensive examples). In particular I am thinking of plpgsql. One
> example is information about working with Exceptions (postgresql specific)
> and another is the small amount of info about the RAISE Statement.
>
> Refering to my mention of exceptions above, the following is information
> that I could not find in the standard docs:
> How to use(Return using RAISE) the actual exception code and message once
> you have handled the error. This is especially usefull if you have used
> WHEN OTHERS to catch the error.
>
> Thanks
> Craig
>
> > On Thu, Mar 24, 2005 at 14:37:59 +0200,
> > postgresql@bryden.co.za wrote:
> >> Hi
> >>
> >> I am new to PostgreSQL and find that the standard documentation is very
> >> thin. I would like to buy a more comprehensive book. All the available
> >> books seem very out of date!!! Firstly, does it matter if I buy a book
> >> that was published in Feb 2003? Will such a book be hopelessly out of
> >> date?
> >
> > What parts of the documentation do you find thin? Without knowing what
> > you need extra info on, it will be hard to recommend other
documentation.
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faq
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>