On Thu, Feb 08, 2001 at 11:36:38PM -0500, Vince Vielhaber wrote:
On 8 Feb 2001, Ian Lance Taylor wrote:
Unfortunately, the license [to splogger] probably precludes
including it with Postgres. Fortunately, it's only 72 lines long, and
would be trivial to recreate.
I missed most of
Hi,
I have deleted the include of termios.h in include/port/qnx4.h.
Then I recompiled pgsql and I have compiled a program with ecpg.
All seem to work right.
Thanks
Maurizio
.
- Original Message -
From: "Tom Lane" [EMAIL PROTECTED]
To: "Maurizio" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED];
Tom Lane wrote:
However, that answers Lamar's complaint about needing a way to control
the syslog level of messages. splogger might be more useful than logger
for our purposes --- even if we have to carry it along with us. What's
its license? A slight tweak of splogger to recognize our
Attached is a list of open source code and documentation items for 7.1.
If people can just confirm completed items, I will remove them right
away. The current version of this file can be seen at:
ftp://candle.pha.pa.us/pub/postgresql/open_items
Tom Lane writes:
Tatsuo Ishii [EMAIL PROTECTED] writes:
There are still many loggings using just plain fprintf(). They should
be replaced by elog(DEBUG) or elog(NOTICE), IMHO.
I don't disagree with doing that where it's convenient and safe (which
is not everywhere). I'm just pointing
Bruce Momjian writes:
Source Code Changes
---
Fix ipcclean on Linux
It's fixed. Or what is the problem?
unixODBC
This would be a new feature. I'm having some private conversation with
the unixODBC maintainer about how to handle this. We'll work on it for
7.2.
Bruce Momjian [EMAIL PROTECTED] writes:
Attached is a list of open source code and documentation items for 7.1.
I've got two major TODO items that are not in your list, but should be:
* visibility of joined columns in JOIN clauses (Thomas thinks code is
wrong, I'm not sure yet)
* separate
Bruce Momjian writes:
Source Code Changes
---
Fix ipcclean on Linux
It's fixed. Or what is the problem?
The issue was that the ipcs code did not work on Linux. In fact,
reference to variable $ipcs_pid doesn't even work because it is not
defined. I believe you
Store all large objects in a single table (Denis Perchine, Tom)
Hmmm... If you would point me to the document where changes should be done, I
will do them.
--
Sincerely Yours,
Denis Perchine
--
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
I wrote:
"Vadim Mikheev" [EMAIL PROTECTED] writes:
Btree uses spins to lock buffers (as all other access methods) and so
I could use only spins in new code. And though tree recovery locks buffers
for longer time than normal insert operations it's possible to get
"stuck" spins when using
Hm. It was OK to use spinlocks to control buffer access when the max
delay was just the time to read or write one disk page. But it sounds
like we've pushed the code way past what it was designed to do. I think
this needs some careful thought, not just a quick hack like increasing
I have no idea. If we mention the existance of separate large object
files, they it has to be updated. If we don't mention it, then we can
remove the item.
[ Charset ISO-8859-1 unsupported, converting... ]
Store all large objects in a single table (Denis Perchine, Tom)
Hmmm... If you
Bruce Momjian [EMAIL PROTECTED] writes:
Our spinlocks don't go into an infinite test loop, right? They back off
and retest at random intervals.
Not very random --- either 0 or 10 milliseconds. (I think there was
some discussion of changing that, but it died off without agreeing on
anything.)
On Fri, Feb 09, 2001 at 01:23:35PM -0500, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Our spinlocks don't go into an infinite test loop, right? They back off
and retest at random intervals.
Not very random --- either 0 or 10 milliseconds. (I think there was
some discussion
Hm. It was OK to use spinlocks to control buffer access when the max
delay was just the time to read or write one disk page. But it sounds
Actually, btree split requires 3 simult. buffers locks and after that
_bt_getstackbuf may read *many* parent buffers while holding locks on
2 buffers.
I have applied the following patch to remove the assumption that
xinv/xinx files are large objects. They are now all stored in
pg_largeobject, so there is no query anymore that dumps out a list of
them. Do we need to find another way to handle a large object listing
from jdbc?
Also, should we
ODBC still has code to handle 6.2 backends:
/* This startup packet is to support pre-Postgres 6.3 protocol */
typedef struct _StartupPacket6_2
{
unsigned intauthtype;
chardatabase[PATH_SIZE];
char
At 12:26 9/02/01 -0500, Bruce Momjian wrote:
Overhaul pg_dump (Philip Warner)
New pg_dump tar output option (Philip)
New pg_dump of large objects (Philip)
New pg_restore command (Philip)
The SGML docs for these have been there for a while - is there something
else I need to do?
Since there were no comments, I'm going to make fast shutdown the default.
I wrote:
Now that waiting for shutdown is the default, it seems that the default
shutdown mode should also be one where there's a high chance of the
shutdown actually happening. As it stands, if there are connected
At 12:26 9/02/01 -0500, Bruce Momjian wrote:
Overhaul pg_dump (Philip Warner)
New pg_dump tar output option (Philip)
New pg_dump of large objects (Philip)
New pg_restore command (Philip)
The SGML docs for these have been there for a while - is there something
else I need to do?
No, I
I have committed changes implementing the plan I sketched yesterday.
A basic install now installs just the include files needed for
client-side programming; to get all the include files, also say
make install-all-headers
I have verified that the header files installed by default are
I am having problems linking ODBC on bsdi. They look like crt1.o
symbols. Any ideas? Libpq links with a similar line, and works fine.
---
#$ gmake
/usr/bin/ld -shared -soname libpsqlodbc.so.0 -Bsymbolic info.o bind.o
Here's the latest version of the pg_logger utility.
The particular questions that come to my mind are:
1. Do the prefixes it watches for match what PG produces?
2. Should it log to LOG_LOCAL1 or to some other LOG_LOCALn?
3. Is the ident string ("postgresql") right?
4. Are the openlog() args
[EMAIL PROTECTED] (Nathan Myers) writes:
4. Are the openlog() args right? (E.g. should it ask for LOG_PID too?)
LOG_PID seems useless, since that would give you the PID of the logger
process, not of the originating backend ...
regards, tom lane
"Steve Shaffer" [EMAIL PROTECTED] writes:
Pgsql v7.1 beta4
ODBC v6.50.00.00
RedHat v6.2
I upgraded from 7.03 to 7.1 beta4 yesterday see the following problem.
After the upgrade, applications like Crystal Reports, MS Query, Brio, etc.
now do not see the catalog of tables and
Bruce Momjian writes:
Allow location of Unix domain socket to be configurable (David J. MacKenzie)
Allow postmaster to listen on a specific IP address (David J. MacKenzie)
Allow socket path name to be specified in hostname by using leading slash
(David J. MacKenzie)
Allow CREATE DATABASE to
I have applied the following patch to properly exit ODBC. I also
patched the ODBC makefile so it links under BSD/OS. The -Bsymbolic
under BSD/OS is very harsh under BSD/OS, requiring all symbols even in
libc and crt1.o to be resolved before creating the shared library.
My 'ld' manual says:
separate client- and server-side includes, make optional install
target to install all of src/include
This is done now, at least as far as the source tree goes (dunno
how Lamar plans to handle it in the RPMs).
New file format for COPY BINARY (Tom)
Already documented, see COPY reference
Items removed. Thanks.
separate client- and server-side includes, make optional install
target to install all of src/include
This is done now, at least as far as the source tree goes (dunno
how Lamar plans to handle it in the RPMs).
New file format for COPY BINARY (Tom)
-Original Message-
From: Peter Eisentraut
Since there were no comments, I'm going to make fast shutdown the default.
Oh I've misunderstood.
I object to the change.
Regards,
Hiroshi Inoue
30 matches
Mail list logo
