-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 22:18
To: Robert Treat
Cc: Alvaro Herrera; Dave Page; Josh Berkus;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [pgsql-www] [HACKERS] Changes to Contributor List
Let me ask you
Usually db works fine stable months, but couple days ago
it was PANIC, and i have no ideas why this happen.
Nov 5 20:22:30 monstr postgres[16071]: [1] LOG: connection received: host=[local]
Nov 5 20:22:30 monstr postgres[16071]: [2] LOG: connection authorized: user=ant
database=tele
Nov 5
sorry , guys, for my english
i meant enterprise db in subj, not enterprice :)
On Fri, 7 Nov 2003, Andriy Tkachuk wrote:
Usually db works fine stable months, but couple days ago
it was PANIC, and i have no ideas why this happen.
Nov 5 20:22:30 monstr postgres[16071]: [1] LOG: connection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've been using libpqxx to access a Postgres database for the last few
months, and I wrote a set of classes to wrap around libpqxx, which
gradually evolved into a small set of classes and class templates.
These allow database tables and rows
Greg Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Have you considered having the background writer check the pages it is
about to write to see if they can be added to the FSM, thereby reducing
the need for vacuum? Seems we would need to add a statistics parameter
so
Well the current argument aside, I do find it discouraging that there is
a considerable difference between the four sites, advocacy, gborg, dev,
and the main site, not only in form but in substance.
I am listed on the dev site as a major contributor, but not on the
advocacy site. Where was the
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems. And as Gaetano pointed out
correctly, we will see wildforms with one or the other feature applied.
I'd believe that for
On Fri, 2003-11-07 at 06:32, Andreas Grabmüller wrote:
Hi all,
well, the most of the programming itself is done, what's currently missing is
1) Some fine tuning on the layout
2) Adding the static pages
3) Translating the pages, news, events etc. into german and maybe some other
Josh Berkus wrote:
Peter,
Btw., what process is used to determine which organizations become a
recognised contributor?
Yeah, that's another ToDo item ... your company needs to go up there.
Criteria are major code contributions and/or sponsoring a full-time developer.
We've
Robert Treat writes:
I disagree... the tech and the content are separate issues, let's keep
them that way or we'll never make progress on either of them.
Just because one solution is technically more simple, it doesn't mean that
it is the overall best solution.
--
Peter Eisentraut [EMAIL
Christopher Kings-Lynne wrote:
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a new section titled Contributors
Emeritus or some such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
I think the Emeritus
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Thu, Nov 06, 2003 at 11:42:13AM -0500, Tom Lane wrote:
I don't have a problem with switching from $1 to tablename_$1, or
some such, for auto-generated constraint names. But if it's not
guaranteed unique, does it really satisfy
Imagine this discussion with your boss:
You: I want to spend an hour a day at work on PostgreSQL
community work.
Boss: Hmm. (How do I justify this?)
You: Our company will be listed on the main PostgreSQL web
site.
Boss: Fine. (That
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Bruce Momjian) wrote:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems. And as Gaetano pointed out
correctly, we
Andrew Sullivan wrote:
On Thu, Nov 06, 2003 at 09:08:57PM +0100, Peter Eisentraut wrote:
I think that list is a pretty dumb idea in the first place. We have a
list of developers with company names next to them. Let readers make
their own recognition evaluation.
I'm not sure that's
On Thu, Nov 06, 2003 at 09:57:12PM +0100, Peter Eisentraut wrote:
True, but for that you're looking at the wrong list. This is the list of
contributors, not of users.
I tend to agree with that. Maybe the trick is to talk about
featured users or something? I dunno, I keep trying to keep the
Bruce Momjian wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Thu, Nov 06, 2003 at 11:42:13AM -0500, Tom Lane wrote:
I don't have a problem with switching from $1 to tablename_$1, or
some such, for auto-generated constraint names. But if it's not
guaranteed
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
regression=# create table foo (f1 int check (f1 0) check (f1 10));
ERROR: check constraint foo_f1 already exists
Is this a TODO to fix?
Probably should be. I'd be inclined to try to fix it by generating
foo_f1_1, foo_f1_2, etc until
Andrew Sullivan wrote:
On Thu, Nov 06, 2003 at 09:57:12PM +0100, Peter Eisentraut wrote:
True, but for that you're looking at the wrong list. This is the list of
contributors, not of users.
I tend to agree with that. Maybe the trick is to talk about
featured users or something? I
Christopher Browne wrote:
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Bruce Momjian) wrote:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems. And as
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
regression=# create table foo (f1 int check (f1 0) check (f1 10));
ERROR: check constraint foo_f1 already exists
Is this a TODO to fix?
Probably should be. I'd be inclined to try to fix it by generating
Bruce Momjian wrote:
Greg Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Have you considered having the background writer check the pages it is
about to write to see if they can be added to the FSM, thereby reducing
the need for vacuum? Seems we would need to add a statistics parameter
Verbus Counts [EMAIL PROTECTED] writes:
Can you show us the stack trace ?
Here is:
Hm, getaddrinfo() is crashing?
Does HPUX 11 have more fields in struct addrinfo than are initialized in
lines 189-196 of src/backend/postmaster/pgstat.c, viz
hints.ai_flags = AI_PASSIVE;
Bruce Momjian wrote:
Jan Wieck wrote:
If the system is write-bound, the checkpointer will find that many dirty
blocks that he has no time to nap and will burst them out as fast as
possible anyway. Well, at least that's the theory.
PostgreSQL with the non-overwriting storage concept can never
Andriy Tkachuk [EMAIL PROTECTED] writes:
Nov 5 20:22:42 monstr postgres[16071]: [3] PANIC: open of
/usr/local/pgsql/data/pg_clog/0040 failed: No such file or directory
Could we see ls -l /usr/local/pgsql/data/pg_clog/
regards, tom lane
On Fri, Nov 07, 2003 at 10:24:04AM -0500, Bruce Momjian wrote:
Maybe a developer of the month feature. :-)
It would be quite cool if, say, General Bits could ocassionaly carry an
interview with a Postgres developer.
(Now that would be a mess to translate)
--
Alvaro Herrera
Christopher Browne wrote:
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Bruce Momjian) wrote:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems. And as Gaetano
Andrew Dunstan [EMAIL PROTECTED] writes:
I think there are several of them from this thread:
. make autogenerated column constraint names unique per table (by adding
_$n ?)
Check.
. add tableoid or tablename to information_schema.{check_constraints,
referential_constraints} (I think
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
If the system is write-bound, the checkpointer will find that many dirty
blocks that he has no time to nap and will burst them out as fast as
possible anyway. Well, at least that's the theory.
PostgreSQL with the
Bruce Momjian wrote:
Jan Wieck wrote:
What doing frequent fdatasync/fsync during a constant ongoing checkpoint
will cause is to significantly lower the physical write storm happening
at the sync(), which is causing huge problems right now.
I don't see that frankly because sync() is syncing
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
. add tableoid or tablename to information_schema.{check_constraints,
referential_constraints} (I think those are the only places where it
would be needed, from my quick skimming).
. add tableoid or tablename to autogenerated table
Jan Wieck [EMAIL PROTECTED] writes:
I am not really aiming at removing sync() alltogether.
...
What doing frequent fdatasync/fsync during a constant ongoing checkpoint
will cause is to significantly lower the physical write storm happening
at the sync(), which is causing huge problems right
Jan Wieck [EMAIL PROTECTED] writes:
However, I have not seen much evidence yet that the vacuum delay alone
does that much.
Gaetano and a couple of other people did experiments that seemed to show
it was useful. I think we'd want to change the shape of the knob per
later suggestions (sleep 10
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
What doing frequent fdatasync/fsync during a constant ongoing checkpoint
will cause is to significantly lower the physical write storm happening
at the sync(), which is causing huge problems right now.
I don't see that
What is the current schedule for RC2/final?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania
This this a new TODO?
---
Jan Wieck wrote:
Gaetano Mendola wrote:
Bruce Momjian wrote:
I can confirm this bug in CVS.
Dropping the pkey from table b in fact drops the unique index from it.
The SPI plan cached
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion, coordination
o Win32
o Talks
o Books/articles
o Web site cleanup
o
On Fri, Nov 07, 2003 at 09:12:50AM -0500, Bruce Momjian wrote:
You: I want to spend an hour a day at work on PostgreSQL
community work.
Boss: Hmm. (How do I justify this?)
You: Our company will be listed on the main PostgreSQL web
site.
Bruce Momjian [EMAIL PROTECTED] writes:
What is the current schedule for RC2/final?
I believe the plan is to wrap RC2 this Sunday evening, and to release
final the following Monday (11/17), barring problems. Core will make
a go/no-go release decision Thursday evening, and if it's go we'll
put a
Bruce Momjian [EMAIL PROTECTED] writes:
This this a new TODO?
No, it's already there, in multiple guises even.
o Fix problems with complex temporary table creation/destruction
without using PL/PgSQL EXECUTE, needs cache prevention/invalidation
* Flush cached query plans when
On Fri, Nov 07, 2003 at 12:16:23PM -0500, Bruce Momjian wrote:
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion, coordination
o Win32
o Talks
o
On Fri, 7 Nov 2003, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
What is the current schedule for RC2/final?
I believe the plan is to wrap RC2 this Sunday evening, and to release
final the following Monday (11/17), barring problems. Core will make
a go/no-go release decision
On Fri, 7 Nov 2003, Bruce Momjian wrote:
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion, coordination
o Win32
o Talks
o Books/articles
Alvaro Herrera wrote:
I don't have an opinion on the Win32 issue.
I do :-)
I think the most important thing for Win32 is for you to set the
direction somewhat (i.e. in more detail than is on your win32 page) and
then jump on Joshua's offer of a dedicated developer (possibly two) to
work on
Alvaro,
That'd be cool for me, but what 'main PostgreSQL web site' are you
talking about? Is this www.postgresql.org? Or advocacy.postgresql.org?
Or maybe it'd be developer.postgresql.org?
I think everyone agrees with the idea of unifying www, advocacy, and
developer. Techdocs and Gborg
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Bruce Momjian wrote:
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion, coordination
o Win32
o Talks
On Fri, Nov 07, 2003 at 10:17:12AM -0800, Josh Berkus wrote:
Alvaro,
That'd be cool for me, but what 'main PostgreSQL web site' are you
talking about? Is this www.postgresql.org? Or advocacy.postgresql.org?
Or maybe it'd be developer.postgresql.org?
I think everyone agrees with the
Bruce Momjian writes:
o TODO/FAQ
The FAQ might as well be maintained just like the rest of the
documentation, i.e., by the development group as a whole.
The TODO list could be replaced by a kind of bug-tracking system with
developer write access only, so developers could keep their
On Fri, 7 Nov 2003, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Bruce Momjian wrote:
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion,
Robert,
on techdocs there is a todo.php file which is probably completely bogus.
theres some indecision on the direction of this site. I would like to
convert the whole thing to CVS, including the wiki pages that comprised the
guides section. others are testing using bricolage to make a new
Peter Eisentraut wrote:
Bruce Momjian writes:
o TODO/FAQ
The FAQ might as well be maintained just like the rest of the
documentation, i.e., by the development group as a whole.
I encourage others to commit to the FAQ.html file in CVS. The only
unique thing I do is to generate the
Tom,
Peter appeared to be asking how additional people could get involved.
Or do you *want* to keep the web group too small to get things done?
Ooops! Sorry, Peter, I *completely* mis-read your e-mail.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
However, I have not seen much evidence yet that the vacuum delay alone
does that much.
Gaetano and a couple of other people did experiments that seemed to show
it was useful. I think we'd want to change the shape of the knob per
later
People occasionally seem to ask for keeping time stamps on schema objects
(tables, functions, etc.) about when they were created and last altered
(in their structure, not the data in the tables). I think that this would
be a relatively useful and painless feature. What do others think?
--
On Fri, 2003-11-07 at 14:00, Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian writes:
o TODO/FAQ
The FAQ might as well be maintained just like the rest of the
documentation, i.e., by the development group as a whole.
I encourage others to commit to the FAQ.html file
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: 07 November 2003 17:37
To: Bruce Momjian
Cc: Peter Eisentraut; Josh Berkus;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [HACKERS] [pgsql-advocacy] Changes to Contributor List
I really think they
-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: 07 November 2003 19:35
To: PostgreSQL Development
Subject: [HACKERS] Timestamps on schema objects
People occasionally seem to ask for keeping time stamps on
schema objects (tables, functions, etc.)
On Fri, 7 Nov 2003, Robert Treat wrote:
On Fri, 2003-11-07 at 14:00, Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian writes:
o TODO/FAQ
The FAQ might as well be maintained just like the rest of the
documentation, i.e., by the development group as a
[EMAIL PROTECTED] (Bruce Momjian) writes:
The worst was my upstairs hallway that had no light fixtures, so late at
night if no other lights were on in the house, you had to walk down the
hallway with your hands out in front of you so you didn't bump into
anything. We had a nightlight in the
- Original Message -
From: Jan Wieck [EMAIL PROTECTED]
Tom Lane wrote:
Gaetano and a couple of other people did experiments that seemed to show
it was useful. I think we'd want to change the shape of the knob per
later suggestions (sleep 10 ms every N blocks, instead of N ms every
Bruce Momjian [EMAIL PROTECTED] writes:
I am not really aiming at removing sync() alltogether. We know already
that open,fsync,close does not guarantee you flush dirty OS-buffers for
which another process might so far only have done open,write. And you
So for what it's worth, though the
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Robert Treat wrote:
I know most people have talked about using bugzilla, but is anyone
familiar with GNATS? I'm currently rereading Open Sources and there's a
paragraph or two mentioning it's use and the fact that it can be
interfaced with
Christopher Browne wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
The worst was my upstairs hallway that had no light fixtures, so late at
night if no other lights were on in the house, you had to walk down the
hallway with your hands out in front of you so you didn't bump into
anything. We
Tom Lane wrote:
While investigating Scott Goodwin's recent report of trouble on Mac OS
X, I have realized that we have an unpleasant little misbehavior in our
last several releases. After a backend crash, the postmaster will
attempt to recycle (delete and recreate) the old shared memory segment.
Greg Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I am not really aiming at removing sync() alltogether. We know already
that open,fsync,close does not guarantee you flush dirty OS-buffers for
which another process might so far only have done open,write. And you
So for what
Christopher Browne wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
The worst was my upstairs hallway that had no light fixtures, so late at
night if no other lights were on in the house, you had to walk down the
hallway with your hands out in front of you so you didn't bump into
Andrew Dunstan [EMAIL PROTECTED] writes:
Bugzilla is far from perfect. But it's getting better.
FWIW, I would like to try a bugzilla-based tracking system for Postgres.
Our last attempt at a tracking system failed miserably, but I think that
was (a) because the software we tried was really
Tom Lane wrote:
Using tableoid instead of tablename avoids renaming problems, but makes
the names horribly opaque IMNSHO.
Agreed. I think using the OIDs would be a horrible choice.
As a point of reference Oracle uses a naming convention of 'C' where
is a sequence generated unique
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
The attached patch fixes the problem by causing the stats collector to
detach from shared memory, which it isn't using anyway.
I seem to recall there once was a pipe from the postmaster to the stat's
processes and closing that will
Barry Lind wrote:
Tom Lane wrote:
Using tableoid instead of tablename avoids renaming problems, but makes
the names horribly opaque IMNSHO.
Agreed. I think using the OIDs would be a horrible choice.
As a point of reference Oracle uses a naming convention of 'C' where
Andrew Dunstan wrote:
Alvaro Herrera wrote:
I don't have an opinion on the Win32 issue.
I do :-)
I think the most important thing for Win32 is for you to set the
direction somewhat (i.e. in more detail than is on your win32 page) and
then jump on Joshua's offer of a dedicated
On Fri, 2003-11-07 at 23:07, Tom Lane wrote:
FWIW, I would like to try a bugzilla-based tracking system for Postgres.
Red Hat has been using a PG-based version of bugzilla for some time.
I'm not sure what the holdup is in getting that work merged back
upstream, but I'd sure like to see it
. if we used bugzilla this might give some impetus to the bugzilla team's
efforts to provide pg as a backend (maybe we could help with that)
I would actually suggest trying RT. It's not primarily a bug tracking system
and there's a bit of an impedance mismatch between a trouble ticketing
On Fri, Nov 07, 2003 at 04:07:46PM -0500, Tom Lane wrote:
Actually, whatever software we pick to run the tracking system,
my guess is that the experiment will not stand or fall on the software.
What we need for success is one or two people who will take
responsibility for housekeeping: putting
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Bugzilla is far from perfect. But it's getting better.
FWIW, I would like to try a bugzilla-based tracking system for Postgres.
Our last attempt at a tracking system failed miserably, but I think that
was (a) because the software we
On Fri, 2003-11-07 at 15:28, Andrew Dunstan wrote:
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Robert Treat wrote:
I know most people have talked about using bugzilla, but is anyone
familiar with GNATS? I'm currently rereading Open Sources and there's a
paragraph or two mentioning
On Fri, 7 Nov 2003, Matthew T. O'Connor wrote:
- Original Message -
From: Jan Wieck [EMAIL PROTECTED]
Tom Lane wrote:
Gaetano and a couple of other people did experiments that seemed to show
it was useful. I think we'd want to change the shape of the knob per
later
Jira is a fantastic bug tracking project management system and is
available free of charge for open source projects.
http://www.atlassian.com/software/jira/
Dave
On Fri, 2003-11-07 at 16:48, Andrew Sullivan wrote:
On Fri, Nov 07, 2003 at 04:07:46PM -0500, Tom Lane wrote:
Actually, whatever
Robert Treat wrote:
On Fri, 2003-11-07 at 15:28, Andrew Dunstan wrote:
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Robert Treat wrote:
I know most people have talked about using bugzilla, but is anyone
familiar with GNATS? I'm currently rereading Open Sources and there's a
Dave Cramer wrote:
Jira is a fantastic bug tracking project management system and is
available free of charge for open source projects.
http://www.atlassian.com/software/jira/
Wow, that looks very cool indeed! And they are Aussies to boot! :-)
cheers
andreew
Tom Lane wrote:
Bugzilla already does email output (ie, notify you of changes to bug
entries you're interested in) well enough. We thought during the last
go-round that it was important to have email input so we could allow
mail to pgsql-bugs to go directly into the tracking system, but in
People occasionally seem to ask for keeping time stamps on schema objects
(tables, functions, etc.) about when they were created and last altered
(in their structure, not the data in the tables). I think that this would
be a relatively useful and painless feature. What do others think?
It has
At 02:59 AM 8/11/2003, Tom Lane wrote:
These are mutually exclusive --- I see no reason to do both.
Not sure that's true; we've taken te design decision to make allow
user-defined constraint names to be non-unique. Given that, I think we
should allow people who fall into the trap to be able to
On Fri, 7 Nov 2003, Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Bugzilla is far from perfect. But it's getting better.
FWIW, I would like to try a bugzilla-based tracking system for Postgres.
Our last attempt at a tracking system failed miserably, but I think that
was (a)
Andrew Dunstan [EMAIL PROTECTED] writes:
Dave Cramer wrote:
Jira is a fantastic bug tracking project management system and is
available free of charge for open source projects.
Wow, that looks very cool indeed! And they are Aussies to boot! :-)
But they don't seem to be on the
Andrew Dunstan [EMAIL PROTECTED] writes:
The last comment on the bug page says:
The Red Hat guys did a quick 'n dirty port. It works, but doesn't
quite make use of the best of PostgreSQL. Also, their tarball is out
of date with the current schema used by Bugzilla.
The bug is actually
Bob Ippolito [EMAIL PROTECTED] writes:
Here's my notes on how to build PostgreSQL 7.4 (CVS) on OS X 10.3
(7B85) with (seems to be working, but I haven't really ran any tests)
python, tcl, perl, readline.
I have just in the past couple hours realized that ps_status.c is
seriously broken on
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
Bob Ippolito [EMAIL PROTECTED] writes:
Here's my notes on how to build PostgreSQL 7.4 (CVS) on OS X 10.3
(7B85) with (seems to be working, but I haven't really ran any tests)
python, tcl, perl, readline.
I have just in the past couple hours realized
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3. It appears that Apple has randomly
decided to start #define'ing BSD,
__APPLE__ is usually the only define you
The doesn't quite make the best use of PG quote is one of the best
examples of buck-passing I've seen in awhile. If Bugzilla had been
designed with some thought to DB independence to start with, we'd not
be having this discussion.
You have to laugh at an app that actually uses MySQL's
On Nov 8, 2003, at 1:00 AM, Tom Lane wrote:
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3. It appears that Apple has randomly
decided to start #define'ing BSD,
I don't remember what we did with -lbind, but if someone shows up with
BeOS, we will get it working.
---
Palle Girgensohn wrote:
Was this problem fixed? Can I request the problem report @ FreeBSD to be
closed?
Thanks,
Tom sent a mail indicating it was fixed. Thanks,
Palle
--On fredag, november 07, 2003 09.32.54 -0500 Bruce Momjian
[EMAIL PROTECTED] wrote:
I don't remember what we did with -lbind, but if someone shows up with
BeOS, we will get it working.
Hi everybody, can anyone tell me if there's a way to retrieve the select
instruction executed from the catalogs, or maybe via some structure in a
trigger?
The reason is that i have some selects constructed on-the-fly (just part of
it) and i want to save that in a table in order to know what
94 matches
Mail list logo
