I have just done the first iteration of a perl script that will take a
log file (not syslog yet) and parse it into timestamp, pid, dbname,
keyword and details (timestamp, pid and dbname optional), accumulating
continuation lines. It will then either write out split files based on
dbname, or loa
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > First get your own platforms enabled for the existing thread flag, and
> > we can revisit this when most/all our platforms are supported. We want
> > to avoid confusion of having things work for some platforms and not
> > others with no way to
On Tue, 5 Aug 2003, Andrew Dunstan wrote:
>
> (Responding to the deafening silence regarding my posts a couple of days
> ago about logging dbnames and disconnections) ;-)
>
> The dbname patch is now done. If nobody objects to the format
> ("[db:yourdbname]") I'll submit it - I did it that way
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I'm prepared to be guided by concensus, though.
I'm not dead set on it either, just wanted to raise a flag. Who else
has an opinion?
regards, tom lane
---(end of broadcast)---
TI
Robert Creager wrote:
psql:dbTriggers.sql:30: ERROR: could not load library
"/usr/local/pgsql/triggers/tassiv_triggers.so":
/usr/local/pgsql/triggers/tassiv_triggers.so: undefined symbol: elog
Am I missing something? I was previously running 7.3.3...
elog is defined now as a macro (in utils/elog.
On Wed, 6 Aug 2003, Merlin Moncure wrote:
> Is it feasible and/or advantageous to move all the system tables to a
> system schema (to "system" or "pg_system")? This seems a much more
> natural place for this type of information. This would remove the
> artificial 'pg_' restriction on class names
--On Tuesday, August 05, 2003 10:36:32 -0400 Bruce Momjian
<[EMAIL PROTECTED]> wrote:
Oh, yes. Let me add that. I didn't realize that was a change of enough
significance.
How is this?
Prevent timestamp from supressing ':00' seconds display
Yes, considering that it's a format change and Tom
This should be on the otyher lists, novice or general for example but here is
your answer anyway.
SELECT item, location FROM foo GROUP BY item,location HAVING count(item) >1
AND count(location) > 1;
On Wednesday 06 August 2003 12:05, The Pennant Shop wrote:
> Hi ,
>
> I have a table:
> item
I said:
> The random component should already help to scatter the wakeups pretty
> well, so I'm thinking about just
> if (oldtime > 1 sec)
> time = 10msec
> else
> time = oldtime + oldtime * rand()
> ie random growth of a maximum of 2x per try, and reset to m
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > ... And of course, we already have pid and timestamp, so once
> > we are done, we will have seven possible data items on each line, and
> > with booleans there will be no control over their order on the line.
>
> Which is exactly the
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> One of the reasons for not doing conversion in binary mode is to have an
>> escape hatch for unconvertible characters, eg for dump purposes.
> That functionality is already provided by setting the client encoding to
> SQL_ASCII.
H
Hi ,
I have a table:
item location
aaa 10
aaa 20
bbb 10
bbb 10
ccc 10
ccc 20
I need to select distinct items where locations are
the same. So result set should look like:
item loation
bbb 10
Already spent 7 hours on this one.
Thanks a lot / Alex
__
Larry Rosenman <[EMAIL PROTECTED]> writes:
> sys/socket.h:#define shutdown _shutdown
Mph. I wonder if any other platforms do that? Well, I'd better assume
that shutdown isn't a safe name for a globally visible field. I'll
rename it.
regards, tom lane
--
Is it feasible and/or advantageous to move all the system
tables to a system schema (to “system” or “pg_system”)?
This seems a much more natural place for this type of information. This would remove the artificial ‘pg_’
restriction on class names and simplify the overall system a little b
"Jenny -" <[EMAIL PROTECTED]> writes:
> so even though the application locks a row in a table, table-level locks are
> automatically taken by postgesql ? why is that?
So that the table doesn't disappear while you're trying to scan it. (Or
afterwards --- a row-level lock wouldn't be noticed by DR
On Tue, 5 Aug 2003, Bruce Momjian wrote:
> How are statement level triggers supposed to work? Are they just
> triggers deferred until the end of the statement? You mentioned access
> to the affected rows, but I don't understand how that is supposed to
> happen.
ILTM like you're supposed to (opt
[EMAIL PROTECTED] wrote:
> I received the following note from the original author of dbf2pg:
>
> > Date: Tue, 05 Aug 2003 18:43:22 +0400
> > From: Maarten Boekhold <[EMAIL PROTECTED]>
> > Subject: Re: status of dbf2pg
> > To: [EMAIL PROTECTED]
> >
> > On 08/03/2003 06:55:01 AM nolan wrote:
> > >
Bruce, the changes you made yesterday to configure for
--enable-thread-safety have broken the build, at least for Linux on
Redhat 9.
Also, I took the opportunity to look at port/threads.c. It is missing
important functionality compaired to the patch I originally
submitted. For getpwuid_r, gethostb
18 matches
Mail list logo
