Palle Girgensohn 11c6621cb5 Fixing problems with the recent security patch: When bison was not ... installed, the patched gram.y file would not be used and the security patch would be a no-op. Also, I've had reports of compilation errors related to bison. Since checking for the correct version of bison is hard and error prone, I'm doing what the postgresql distribution does - patching the yacc:ed .c file to get rid of the building dependency. Bumping portrevision of -server. Pointy hat to: me Noticed by: Mike Harding and others Security: http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html Approved by: seanc (implicit)		2005-02-20 05:38:24 +00:00
..
502.pgsql	Split the postgresql ports into a server and a client part. The	2005-01-31 00:19:47 +00:00
dot.cshrc.in
dot.profile.in
patch-configure
patch-plpython-Makefile	Split the postgresql ports into a server and a client part. The	2005-01-31 00:19:47 +00:00
patch-src-interfaces-jdbc-build-xml
patch-src-interfaces-libpgtcl-Makefile
patch-src-makefiles-Makefile.freebsd
patch-src-pl-plpgsql-src-gram-y	Fix security alert using a patch from PostgreSQL's CVS repository:	2005-02-19 12:07:46 +00:00
patch-src-pl-plpgsql-src-pl-gram-c	Fixing problems with the recent security patch: When bison was not	2005-02-20 05:38:24 +00:00
patch-src:backend:utils:misc:postgresql.conf.sample
pgsql.sh.tmpl
pkgIndex.tcl.in
regresspatch-src-test-regress-pgregress-sh	Split the postgresql ports into a server and a client part. The	2005-01-31 00:19:47 +00:00