| Age | Commit message (Collapse) | Author |
|---|
|
I hope everyone has sys/socket.h.
|
|
|
|
If I have introduced any syntax errors with this, I will patch them in
the morning, and Marc will have a good laugh.
|
|
cache. I found if I manually added a line to flush the whole relation
cache, the assert error disappeared. Looking through the code, I found
that the relation cache is flushed at the end of each query if the
reference count is zero for the relation. However, printf's showed that
the rd_relcnt(reference count) for the accessed query was not returning
to zero after each query.
It turns out the parser was doing a heap_ropen in parser/analyze.c to
get information about the table's columns, but was not doing a
heap_close.
This was causing the query after the ALTER TABLE ADD to see the old
table structure, and the executor's assert was reporting the problem.
|
|
|
|
|
|
|
|
|
|
used in test drivers.
|
|
|
|
correct way to do this. Theoretically you could have a NULL
pointer that isn't represented internally as all 0 bits. This
guarantees that it convert correctly.
Submitted by: darcy@druid.com (D'Arcy J.M. Cain)
|
|
use of long term cooperative locks managed by the user applications.
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
|
|
|
|
|
|
Submitted by: D'Arcy Cain
|
|
|
|
|
|
|
|
my postmaster 1.07.
It's really simple, the loop dealing with all sockets
can't handle more than one ready socket :-)
A simple logic error dealing with lists.
OR IS THERE ANY REASON FOR SETTING curr TO 0?
Submitted by: Carsten Heyl <Heyl@nads.de>
|
|
|
|
|
|
Added NOTICE messages for bad table names.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To: Postgres95-development <pg95-dev@ki.net>
Subject: [PG95-DEV] postgres.h patch
This removes the parameters from the func_ptr prototype in postgres.h in
2.0.
|
|
./utils/adt/varlena.c
- --- ../../../orig/postgres95/src/backend/utils/adt/varlena.c Mon Jul 22
23:56:04 1996
+++ ./utils/adt/varlena.c Tue Sep 17 15:12:55 1996
@@ -166,7 +166,7 @@
if (inputText == NULL)
return(NULL);
- - len = strlen(inputText) + VARHDRSZ;
+ len = strlen(inputText) + VARHDRSZ + 1 /* terminating 0 */;
result = (struct varlena *) palloc(len);
VARSIZE(result) = len;
memmove(VARDATA(result), inputText, len - VARHDRSZ);
Submitted by: skimo@breughel.ufsia.ac.be (Sven Verdoolaege)
|
|
./libpq/be-fsstubs.c
- --- ../../../orig/postgres95/src/backend/libpq/be-fsstubs.c Tue Jul 9
08:21:30 1996
+++ ./libpq/be-fsstubs.c Tue Sep 17 15:30:09 1996
@@ -241,7 +241,7 @@
*/
fd = open(VARDATA(filename), O_RDONLY, 0666);
if (fd < 0) { /* error */
- - elog(WARN, "lo_import: can't open unix file\"%s\"\n", filename);
+ elog(WARN, "lo_import: can't open unix file \"%s\"\n",
VARDATA(filename));
}
/*
Submited by: skimo@breughel.ufsia.ac.be (Sven Verdoolaege)
|
|
way one creates a database system. Parts that were in "make install"
are not either in "make all" or initdb. Nothing goes in the PGDATA
directory besides user data. Creating multiple database systems is
easier.
In addition to applying the patch, it is necessary to move the file
libpq/pg_hba to backend/libpq/pg_hba.sample.
Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
|
|
--- src/backend/storage/file/fd.c Thu Sep 12 17:23:38 1996
***************
*** 262,268 ****
Delete(file);
/* save the seek position */
! fileP->seekPos = lseek(fileP->fd, 0L, SEEK_CUR);
Assert( fileP->seekPos != -1);
/* if we have written to the file, sync it */
--- 262,268 ----
Delete(file);
/* save the seek position */
! fileP->seekPos = (long) lseek(fileP->fd, 0L, SEEK_CUR);
Assert( fileP->seekPos != -1);
/* if we have written to the file, sync it */
Submitted by: Randy Terbush <randy@zyzzyva.com>
|
|
|with gram.c and parser.h.
|
|--
|Bryan Henderson Phone 408-227-6803
|San Jose, California
|
|
|
|
|
ppl are seeing with v2.0
|
|
of the array constants and in one of the loadable modules I posted some time
ago.
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
|
|
Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
|
|
- Added the header access/heapam.h.
- Changed all instances of "length" to "data_length" to quiet
the compiler.
- initialized a few variables. The compiler couldn't see that
the code guaranteed that these would be initialized before
being dereferenced. If anyone wants to check my work follow
the usage of these variables and make sure that this true
and wasn't actually a bug in the original code.
- added a missing break statement to a default case. This
was a benign error but bad style.
- layed out heap_sysattrlen differently. I think this way
makes the structure of the code crystal clear. There should
be no actual difference in the actual behaviour of the code.
Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
|
|
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
Submitted by: "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
|
|
current state of development...namely, we are on 2.0
NOTE:
BTW, the is also a check in postmaster which won't let you use an older
version of the database by checking the version number. The version number
of a database is in data/PG_VERSION (a plain ASCII file).
- Andrew
|
|
|
|
execute an sql function containing an utility command (create, notify, ...).
The bug is part in the planner, which returns a number of plans different
than the number of commands if there are utility commands in the query, and
in part in the function executor which assumes that all commands are normal
query commands and causes a SIGSEGV trying to execute commands without plan.
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
|
|Here's a patch for Version 2 only. It just adds an Assert to catch some
|inconsistencies in the catalog classes.
|
|--
|Bryan Henderson Phone 408-227-6803
|San Jose, California
|
|
|
The problem is that the function arguments are not considered as possible key
candidates for index scan and so only a sequential scan is possible inside
the body of a function. I have therefore made some patches to the optimizer
so that indices are now used also by functions. I have also moved the plan
debug message from pg_eval to pg_plan so that it is printed also for plans
genereated for function execution. I had also to add an index rescan to the
executor because it ignored the parameters set in the execution state, they
were flagged as runtime variables in ExecInitIndexScan but then never used
by the executor so that the scan were always done with any key=1. Very odd.
This means that an index rescan is now done twice for each function execution
which uses an index, the first time when the index scan is initialized and
the second when the actual function arguments are finally available for the
execution. I don't know what is the cost of an double index scan but I
suppose it is anyway less than the cost of a full sequential scan, at leat
for large tables. This is my patch, you must also add -DINDEXSCAN_PATCH in
Makefile.global to enable the changes.
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
