"Vadim Mikheev" <[EMAIL PROTECTED]> writes:
> Shouldn't we increase S_MAX_BUSY and use ERROR instead of FATAL?
>>
>> No. If you have delays exceeding a minute, or that are even a visible
>> fraction of a minute, then a spinlock is NOT the correct mechanism to be
>> using to wait ... because guess
On 8 Feb 2001, Ian Lance Taylor wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
>
> > So now the question is, why did they write splogger?
>
> ``They'' didn't write splogger. Dan Bernstein did. It's part of the
> qmail distribution. Unfortunately, the license probably precludes
> including i
[EMAIL PROTECTED] (Nathan Myers) writes:
> So now the question is, why did they write splogger?
``They'' didn't write splogger. Dan Bernstein did. It's part of the
qmail distribution. Unfortunately, the license probably precludes
including it with Postgres. Fortunately, it's only 72 lines lo
On Thu, 8 Feb 2001, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > The Linux page says just:
> > HISTORY
> >A syslog function call appeared in BSD 4.2.
> > Normally if there's a standard they mention it.
>
> Yes, the HP man pages also trace it to BSD. I'm surprised sys
[EMAIL PROTECTED] (Nathan Myers) writes:
> So now the question is, why did they write splogger? splogger parses
> the beginning of each message to assign a severity; if it finds "alert:"
> or "warning:" it assigns those, or "info" otherwise. To make splogger
> useful you have to know it's lis
On Thu, Feb 08, 2001 at 05:50:55PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > Not so fast... logger just writes its arguments to syslog. I don't
> > see any indication that it (portably) reads its standard input.
>
> FWIW, the HPUX 10.20 man page for logger sez:
>
>
> > Shouldn't we increase S_MAX_BUSY and use ERROR instead of FATAL?
>
> No. If you have delays exceeding a minute, or that are even a visible
> fraction of a minute, then a spinlock is NOT the correct mechanism to be
> using to wait ... because guess what, it's spinning, and consuming
> processo
Hi all,
I'm starting to program with the SPI interface with PG 7.0.3. I can get
everything to work up until I use SPI_exec (successfully) using a query
like 'SELECT foobar, baz1 from test1'.
The return code from SPI_exec indicates SPI_OK_SELECT and the variable
SPI_processed is 2 (meaning there
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 out that we need a sol
> > Precisely my point. I think working hard on syslog support inside elog
> > is misplaced effort.
>
> Well, I can think of a few things:
> 1.) Some messages are more important than others. Syslog levels are
> useful to segreggate debug, errors, informational, and critical
> messages.
> 2.)
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> This is only part of a larger problem, namely that over time it gets more
> likely that some public header file will depend on config.h. For example,
> the libpq++ one's already do. The SSL support in libpq currently requires
> the user to define US
Tom Lane writes:
> where the include files have these roles:
This plan looks good in general. It's the same I've been pondering for a
while. But maybe this should receive more extensive thought than what
would be appropriate to implement now.
> postgres_ext.h: definitions needed in frontend,
On Thu, 8 Feb 2001, Tom Lane wrote:
> Alex Pilosov <[EMAIL PROTECTED]> writes:
> > when I include files needed for SPI, it drags also a lot of other
> > garbage in, which conflicts with other things (namely, trying to get a
> > file to simultaneously include SPI and perl headers is impossible).
Alex Pilosov <[EMAIL PROTECTED]> writes:
> when I include files needed for SPI, it drags also a lot of other
> garbage in, which conflicts with other things (namely, trying to get a
> file to simultaneously include SPI and perl headers is impossible).
> I realise it might be a lot of pain to clea
On Thu, 8 Feb 2001, Alex Pilosov wrote:
> Great! :)
>
> It might also clean up something that I've been fighting against for
> awhile: when I include files needed for SPI, it drags also a lot of other
> garbage in, which conflicts with other things (namely, trying to get a
> file to simultaneous
[EMAIL PROTECTED] (Nathan Myers) writes:
> Not so fast... logger just writes its arguments to syslog. I don't
> see any indication that it (portably) reads its standard input.
FWIW, the HPUX 10.20 man page for logger sez:
A message can be given on the command line, which is logged
i
On Fri, 9 Feb 2001, Oleg Bartunov wrote:
> We plan to develope sample application - searching postgres mail archives
> ( I have collection from 1995) and present it for testing. If people will
> happy with performance and quality of results we could install it
> on www.postgresql.org.
You tell m
I have been looking at making a split between client-side and server-side
include files as we discussed earlier this week (pghackers thread
"Include files for SPI are not installed", if you missed it). It turns
out that the major issue here is not just divvying up the files; the
problem is that w
On Thu, Feb 08, 2001 at 04:00:12PM -0500, Lamar Owen wrote:
> "Dominic J. Eidson" wrote:
> > On Thu, 8 Feb 2001, Lamar Owen wrote:
> > > A syslogger of stderr would make a nice place to pipe the output :-).
> > > 'postmaster 2>&1 | output-to-syslog-program -f facility.desired' or
>
> > 2>&1
On Thu, Feb 08, 2001 at 02:43:33PM -0500, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > There are still scads of fprintf(stderr, "some error message from
> > postmaster or backend") lying around, in CURRENT as of this morning at
> > 1:00AM EDT. Some are things such as the usage mes
On Thu, 8 Feb 2001, Dominic J. Eidson wrote:
> On Thu, 8 Feb 2001, Lamar Owen wrote:
>
> > A syslogger of stderr would make a nice place to pipe the output :-).
> > 'postmaster 2>&1 | output-to-syslog-program -f facility.desired' or
> > some such. But that obviates the need to support syslog
On Thu, 8 Feb 2001, Ned Lilly wrote:
> (bcc'ed to -hackers)
>
> Gunnar R|nning wrote:
>
> > Does anybody know how Oracle has implemented their "context" search or
> > whatever it is called nowadays ?
>
> They're calling it Intermedia now ... http://www.oracle.com/intermedia/
>
> I have yet to mee
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > AOLserver is one example that successfully redirects dynamic linker
> > messages to it's own log.
> Oh? How? Are you sure they're not just piping stderr to a program
> of their own devising? That's basically what I'm recommending.
"Dominic J. Eidson" wrote:
> On Thu, 8 Feb 2001, Lamar Owen wrote:
> > A syslogger of stderr would make a nice place to pipe the output :-).
> > 'postmaster 2>&1 | output-to-syslog-program -f facility.desired' or
> 2>&1 | logger -p facility.level
[snip]
> Logger provides a shell command
Lamar Owen <[EMAIL PROTECTED]> writes:
> AOLserver is one example that successfully redirects dynamic linker
> messages to it's own log.
Oh? How? Are you sure they're not just piping stderr to a program
of their own devising? That's basically what I'm recommending.
> Is syslog not portable en
On Thu, 8 Feb 2001, Lamar Owen wrote:
> A syslogger of stderr would make a nice place to pipe the output :-).
> 'postmaster 2>&1 | output-to-syslog-program -f facility.desired' or
> some such. But that obviates the need to support syslog _at_all_ in the
2>&1 | logger -p facility.level
mora
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> 2. During tests I've got stuck spin aborts couple of times.
> So I've increased S_MAX_BUSY, placed elog(NOTICE, "WOULD BE STUCK")
> for spins == 20001 in s_lock_sleep() and rerun tests.
> I've got *many* "WOULD BE STUCK" notices but no one abort.
> Do
Bruce Momjian wrote:
> > Given these considerations, I'm not all that excited about mounting a
> > holy war on stdout/stderr messages in the backend code.
Holy War? Not quite -- just a desire for consistency. Not terribly
important -- just cleaning out my over-stuffed inbox.
> > It'd be more
Hi
1. Subj is implemented and is ON by default in current.
There is flag - fixbtree - to turn this feature OFF.
I've run some tests: 100 clients inserted big tuples (1700-1800
bytes) into single table with index. After splitting root page
elog(ERROR) was forced, as well as after each ~ 5th non-ro
> However, it's folly to imagine that we will ever get rid of stderr
> output entirely. One glaring example is that on most platforms,
> if you have a failure while trying to load a dynamic-link library,
> the dynamic linker will emit useful messages (like the names of
> unresolved symbols) on st
Lamar Owen <[EMAIL PROTECTED]> writes:
> There are still scads of fprintf(stderr, "some error message from
> postmaster or backend") lying around, in CURRENT as of this morning at
> 1:00AM EDT. Some are things such as the usage message -- others are
> obviously (IMHO) things that need to be sent
Bruce Momjian wrote:
>
> Can someone address this?
>
> > Bruce Momjian wrote:
> > >
> > > Seems this was already done in 7.1, right?
> > [thread on puts() and fprintf(stderr and printf instead of tprintf or
> > replacement truncated]
> >
> > There are still scads of fprintf(stderr, "some error m
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
clients, pg_ctl will wait for 60 or so seconds before proclaiming that the
postmaster won't
(bcc'ed to -hackers)
Gunnar R|nning wrote:
> Does anybody know how Oracle has implemented their "context" search or
> whatever it is called nowadays ?
They're calling it Intermedia now ... http://www.oracle.com/intermedia/
I have yet to meet an Oracle customer who likes it.
I think there's a
Tom Lane writes:
> So it seems to me that the right approach is for configure to never
> select byacc or yacc by default, but instead to use a 'missing' script
> like we do when flex isn't found. As with the flex case, the user
> could override configure's choice, but if he does then it's his
>
Brent Verner writes:
> I can agree with this approach, unless there is some magic to get
> byacc to work. In any case, there should be a note in the installation
> docs stating that bison must be used when working with the CVS src.
There is.
--
Peter Eisentraut [EMAIL PROTECTED] htt
Brent Verner <[EMAIL PROTECTED]> writes:
> | I wonder if we ought not accept byacc as a suitable yacc in configure?
> I can agree with this approach, unless there is some magic to get
> byacc to work.
It's very probably possible to make it work by feeding byacc enough
table-enlarging options. (
On 07 Feb 2001 at 20:15 (-0500), Tom Lane wrote:
| Vince Vielhaber <[EMAIL PROTECTED]> writes:
| > Now I get:
| > byacc -d preproc.y
| > byacc: f - maximum table size exceeded
| > gmake[4]: *** [preproc.c] Error 2
|
| Better install bison if you want to work with CVS sources ...
| the lack of bi
Josh Berkus wrote:
> Tom, Jan, Michael,
>
> > While I have not looked closely, I seem to recall that plpgsql handles
> > INTO by stripping that clause out of the statement before it's passed to
> > the SQL engine. Evidently that's not happening in the EXECUTE case.
> >
> > Jan, do you agree this
Tom Lane wrote:
> I have looked a little bit at what it'd take to make SELECT INTO inside
> an EXECUTE work the same as it does in plain plpgsql --- that is, the
> INTO should reference plpgsql variables, not a destination table.
> It looks to me like this is possible but would require some nontri
On 7/02/01 at 18:05, JP Sugarbroad <[EMAIL PROTECTED]> wrote:
> Well... still no CORBA? I thought someone would pick it up... then
> again, I haven't seen that many people using it. JDBC seems to be more
> popular...
>
> P.S. Cc: me, I'm not on the list.
>
> --
> Taral <[EMAIL PROTECTED]>
> Pl
> > But the current timestamp does not store a timezone. timestamp with time zone
> > is supposed to store and output the timezone that was inserted.
> > The current timestamp has it messed up (sorry), since it does not store a timezone.
> > It stores time in UTC and always converts output to the
42 matches
Mail list logo
