this should get to the list without any problems ...
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
On 6 Aug 2003 at 9:51, Peter Eisentraut wrote:
Shridhar Daithankar writes:
Can anybody tell me what flags etc. are to be used. I have a slackware 9.0
installation with most of the developer tools I believe. I can give it a shot.
When you configure, enable everything:
--enable-nls
Robert Creager [EMAIL PROTECTED] writes:
Aug 6 16:24:55 thunder postgres[7835]: [11-1] ERROR: variable not
found in subplan target lists
I believe I've fixed this as of cvs tip. Thanks for the test case.
regards, tom lane
---(end of
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:
If we are setting a table level lock
both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the
On Thu, Aug 07, 2003 at 13:16:29 -0700,
Joe Conway [EMAIL PROTECTED] wrote:
Bruno Wolff III wrote:
array_iterator.c:30: utils/fmgroids.h: No such file or directory
make: *** [array_iterator.o] Error 1
I must have caught something in the middle of an update. I grabbed a fresh
copy a little
Bruce Momjian writes:
Actually, your getpwuid_r is the old, pre-POSIX format.
No, his is the right POSIX/SUS variant.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index
After a long battle with technology,
Merlin Moncure [EMAIL PROTECTED], an earthling, wrote:
INAL, but I would read carefully over the Oracle license agreement
and redistribution allowances before doing this, especially if the
database is installed in a commercial environment. With all the
legal
Bruce Momjian [EMAIL PROTECTED] writes:
I am marking the completed TODO items. Are these done?
* Have standalone backend read postgresql.conf
[looks] Nope. No ProcessConfigFile() call in postgres.c.
* Prevent whole-row references from leaking memory, e.g. SELECT
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, thread.c, path.c, and sprompt.c should be in utils, but how do I do
that? Utils seems to be a place things are pulled from, rather than a
library that goes with every link.
Is it worth creating another library that acts just like /port but is
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I am marking the completed TODO items. Are these done?
* Have standalone backend read postgresql.conf
[looks] Nope. No ProcessConfigFile() call in postgres.c.
OK.
* Prevent whole-row references from leaking memory,
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: [EMAIL PROTECTED]|postgresql}.org
---(end of broadcast)---
TIP 8: explain analyze is
Hello:
I want to know if postgresql 7.4 beta 1 can be configured under Cygwin
with SSL support ??
If the answer is positive how can i do it ?? or where can i found
documentation about this ( under linux or cygwin :) ) ??
I have found this on PostgreSQL docs :) i have it configured yet.
--
--On Friday, August 08, 2003 11:53:34 +0100 Lee Kindness
[EMAIL PROTECTED] wrote:
I've not been keeping up with the thread re who has what version of
getpwuid_r... But just to clarify things the right version is:
int getpwuid_r(uid_t uid, struct passwd *pwd, char *buffer,
Alessio Bragadini [EMAIL PROTECTED] writes:
The first beta fails two regression tests
on alphaev67-dec-osf4.0g, compiled by cc -std -std
i.e. Compaq/HP Digital Unix/Tru64/name-of-the-day
They are join (FAILED) and random (failed ignored). Attached is the
regression diff.
AFAICT, the diffs
Stephan Szabo [EMAIL PROTECTED] writes:
On Fri, 8 Aug 2003, Tom Lane wrote:
I have also just traced through _SPI_cursor_operation() in spi.c,
watched PortalRunFetch return 2, and then watched _SPI_checktuples read
zero from _SPI_current-processed. How the heck could that happen?
Compiler
Josh Berkus wrote:
Actually, now that I look at it again, it is referring to procedures,
not functions. Maybe just make it:
o Add capability to create and call PROCEDURES
OK. I need to put a full proposal behind this once 7.4 is in the can.
However, this is largely academic until we get
On Fri, Aug 08, 2003 at 12:15:07PM -0700, Jenny - wrote:
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:
[...]
Is this on a crontab or something? It has gotten very annoying lately.
--
Alvaro Herrera (alvherre[a]dcc.uchile.cl)
Right now the sectors on the hard disk
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Yeah. I'm leaning towards the idea that a protocol addition is what to
do.
I am confused why a protocol change would be desired.
I was thinking that you might want it at a lower level than having to
issue a SQL command to get at the
Gaetano Mendola [EMAIL PROTECTED] writes:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../src/include -c -o execScan.o execScan.c
execScan.c: In function `tlist_matches_tupdesc':
execScan.c:199: warning: unused variable `att_tup'
Looks like you're the first person to
Shridhar Daithankar writes:
Can anybody tell me what flags etc. are to be used. I have a slackware 9.0
installation with most of the developer tools I believe. I can give it a shot.
When you configure, enable everything:
--enable-nls --enable-thread-safety --with-tcl --with-perl --with-python
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Prepared statements would be just as much of a problem. I think the
correct answer is simply don't use those features in a pooled
environment.
Ouch. Double ouch in fact. I'm using prepared statements extensively in
my current
Bruce Momjian [EMAIL PROTECTED] writes:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Some notes on specific items:
Update /tmp socket files regularly to avoid their removal (Tom)
More specifically, update the file mod
Thinking hard about wording...
Add partially implemented FOR EACH STATEMENT statement-level triggers (Neil Conway)
which doesn't look nice but expresses what's implemented. Taken from the
CREATE TRIGGER FOR EACH STATEMENT documentation, a user would think he
could do the same stuff as on lets
On Fri, 8 Aug 2003 16:53:48 -0700, Sean Chittenden
[EMAIL PROTECTED] wrote:
# SHOW effective_cache_size ;
effective_cache_size
--
4456
(1 row)
Only 35 MB? Are you testing on such a small machine?
The stats are attached bzip2 compressed.
Nothing was attached. Did you
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
TODO item?
Yeah. I'm leaning towards the idea that a protocol addition is what to
do.
I put this under Clients:
* Allow clients to query WITH HOLD cursors and prepared statements
I am confused why a protocol change would be
Bruce Momjian writes:
If a file is needed by three non-backend directories, /port seems to be
the proper place for it.
src/port is intended for replacement implementations of standard library
functions. If we make it an everything that is used in more than one
place directory, we should be
Sean Chittenden [EMAIL PROTECTED] writes:
Which suggests to me that line 3964 in
./src/backend/utils/adt/selfuncs.c isn't right for multi-column
indexes, esp for indexes that are clustered. I don't know how to
address this though... Tom, any hints?
Yes, we knew that already. Oliver had
OK, TODO updated.
---
Joe Conway wrote:
Bruce Momjian wrote:
o Add PL/PgSQL PROCEDURES that can return multiple values
Do you have TODO to add for this? I removed the original one because,
as worded, it
I propose to add the following macros for the fields of an error or notice
message for use in libpq applications. The names are modelled after the
ones that ODBC uses. (Well, at least they are chosen not to collide in
case we want to continue on that track.)
S PG_DIAG_SEVERITY
C
Joe Conway [EMAIL PROTECTED] writes:
This one I don't understand:
o Support construction of array result values in expressions
Not sure why you don't understand it, when you did it ;-). It's asking
for the ARRAY[] syntax. Bruce, that one should be marked done.
I thought Peter did something
On Thu, 7 Aug 2003, Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I was just testing the threaded ecpg, and ran some performance tests.
Without using threads, I am seeing 100,000 inserts of a single word into
a simple table take 12 seconds:
CREATE
Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
Tom Lane wrote:
This can already be done by comparing old and new values, no?
No, this is not the case.
UPDATE foo SET x=x, y=y
is different from
UPDATE foo SET y=y
if triggers maintaining x are involved.
Only
On Fri, 8 Aug 2003, Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
the following code was working properly under Postgres 7.3.X
I'm now running my regression test with Postgres 7.4beta1 and I'm
having the error in subj.
I tried this and got
regression=# select bar();
bar
33 matches
Mail list logo
