postgresql/src/tutorial
Tom Lane f933766ba7 Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in
pgsql-hackers.  pg_opclass now has a row for each opclass supported by each
index AM, not a row for each opclass name.  This allows pg_opclass to show
directly whether an AM supports an opclass, and furthermore makes it possible
to store additional information about an opclass that might be AM-dependent.
pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we
previously expected the user to remember to provide in CREATE INDEX commands.
Lossiness is no longer an index-level property, but is associated with the
use of a particular operator in a particular index opclass.

Along the way, IndexSupportInitialize now uses the syscaches to retrieve
pg_amop and pg_amproc entries.  I find this reduces backend launch time by
about ten percent, at the cost of a couple more special cases in catcache.c's
IndexScanOK.

Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane.

initdb forced.
2001-08-21 16:36:06 +00:00
..
advanced.source
basics.source
beard.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
complex.c
complex.source Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in 2001-08-21 16:36:06 +00:00
funcs_new.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
funcs.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
funcs.source Fix some bogosity in the tutorial examples. 2000-03-28 02:49:19 +00:00
Makefile Fix Cygwin build, per Jason Tishler. 2001-08-09 13:52:06 +00:00
README
syscat.source Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in 2001-08-21 16:36:06 +00:00

This directory contains SQL tutorial scripts.  To look at them, first do a
	% make
to compile all the scripts and C files for the user-defined functions
and types.  (make needs to be GNU make and may be named something
different on your system)

Then, run psql with the -s flag:
	% psql -s

Welcome to the POSTGRESQL interactive sql monitor:
  Please read the file COPYRIGHT for copyright terms of POSTGRESQL

   type \? for help on slash commands
   type \q to quit
   type \g or terminate with semicolon to execute query
 You are currently connected to the database: jolly

jolly==>

From within psql, you can try each individual script file by using
the \i <filename> psql command.