Hi everyone,
Have been putting together a tool called "pg_autotune" for automatically
tuning a PostgreSQL database (either local or remote). It does this by
repetitively benchmarking PostgreSQL (using Tatsuo's pgbench code) with
different buffer settings, then fine tuning those settings dependin
Hi all,
I just submitted a project to GBorg. I got it submitted and it told me that
GBorg staff would be back to me after review.
I would love to have a check box on project registration page which asks
whether you have some code to submit or not.
Because in my case I have some..;-)
TIA..
B
Justin Clift <[EMAIL PROTECTED]> writes:
> Have been putting together a tool called "pg_autotune" for automatically
> tuning a PostgreSQL database (either local or remote). It does this by
> repetitively benchmarking PostgreSQL (using Tatsuo's pgbench code) with
> different buffer settings, then
What's the strategy for naming things schema or namespace? In notice that
pg_dump messages are all about namespaces. That seems confusing from a
user's viewpoint.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you
$ postmaster --help
...
Report bugs to <[EMAIL PROTECTED]>.
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
$
This is from a fresh installation, no debugging turned on.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
Tom Lane wrote:
>
> Justin Clift <[EMAIL PROTECTED]> writes:
> > Have been putting together a tool called "pg_autotune" for automatically
> > tuning a PostgreSQL database (either local or remote). It does this by
> > repetitively benchmarking PostgreSQL (using Tatsuo's pgbench code) with
> > dif
Peter Eisentraut dijo:
> $ postmaster --help
> ...
> Report bugs to <[EMAIL PROTECTED]>.
> DEBUG: proc_exit(0)
> DEBUG: shmem_exit(0)
> DEBUG: exit(0)
> $
This is weird:
$ postmaster -d1 --help
FATAL: --help requires argument
$
--
Alvaro Herrera ()
"La espina, desde que nace, ya pincha"
Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Another interesting case is multiple inheritance.
>>
>> create table p1 (f1 int);
>> create table p2 (f1 int);
>> create table c () inherits(p1, p2);
>>
>> drop ONLY column p1.f1;
>> drop column p2.f1;
>>
>> After this sequence, what is the state of
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> What's the strategy for naming things schema or namespace? In notice that
> pg_dump messages are all about namespaces. That seems confusing from a
> user's viewpoint.
Probably the user-visible messages should all mention schemas.
I named the catal
Tom Lane dijo:
> It seems to me that DROP ONLY should set attislocal true on each child
> for which it decrements the inherit count, whether the count reaches
> zero or not. This would cause the behavior in the above case to be that
> c.f1 stays around after the second drop (but can be dropped
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Peter Eisentraut dijo:
>> $ postmaster --help
>> ...
>> Report bugs to <[EMAIL PROTECTED]>.
>> DEBUG: proc_exit(0)
>> DEBUG: shmem_exit(0)
>> DEBUG: exit(0)
>> $
Fixed: someone was sloppy about the initial value of server_min_messages.
> This is w
> On Thu, 19 Sep 2002, Tom Lane wrote:
>> AFAICS, getting SIMILAR TO to operate per spec would require adding some
>> sort of translation function that converts the spec-style pattern into
>> a Posix pattern that our regex match engine would handle.
I did something about this. The translation fu
I had a thought about what to do with the ECPG grammar-too-big problem:
rather than depending on a beta release of bison, we could attack the
problem directly by omitting some of the backend grammar from what ECPG
supports. Surely there are not many people using ECPG to issue obscure
utility comm
Tom Lane wrote:
> I had a thought about what to do with the ECPG grammar-too-big problem:
> rather than depending on a beta release of bison, we could attack the
> problem directly by omitting some of the backend grammar from what ECPG
> supports. Surely there are not many people using ECPG to is
Michael Meskes wrote:
> Hi,
>
> I just removed the prepare/execute/deallocate function from ecpg's
> parser so there are no conflicts anymore. But for the future (that is
> after 7.3 is released) I'd like to work something out. The only problem
> I see with using the backend functions is that the
[ Previous version removed from patches queue..]
Thanks for doing both interfaces.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
When you say:
> So proposal #1 is to rip out the numeric versions of these functions.
you mean remove the ability to do transendentals on numerics to prevent
such unusual auto-casting? Are you suggesting that in all other cases,
autocast to numeric is OK? I am a little confused.
On Fri, 20 Sep 2002, Bruce Momjian wrote:
> In fact, I tried to open a dialog with you on this issue several times,
> but when I got no reply, I had to remove PGXLOG. If we had continued
> discussion, we might have come up with the GUC compromise.
Ya know, I'm sitting back and reading this, an
Marc G. Fournier wrote:
>
> On Fri, 20 Sep 2002, Bruce Momjian wrote:
>
> > In fact, I tried to open a dialog with you on this issue several times,
> > but when I got no reply, I had to remove PGXLOG. If we had continued
> > discussion, we might have come up with the GUC compromise.
>
> Ya kno
> > the hardware. On the other hand I do believe I saw a message
> > recently saying that some of the 2.4 series kernels had file system
> > bugs.
>
> I recall problems, offhand, with 2.4.5, 2.4.10, 2.4.11 (which was so
> broken that you couldn't recover), and 2.4.15. I seem to recall a
> report
> >From /.
>
>
> "Ever since Oracle announced they wouldn't port 9i to NetWare, Novell
> has been scrambling to find an enterprise-capable DB. Now it looks like
> they're settling on PostgreSQL. This follows their decision to ship
> Apache as the default web server for NetWare 6. Linux aficiona
On Sun, 22 Sep 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> >
> > On Fri, 20 Sep 2002, Bruce Momjian wrote:
> >
> > > In fact, I tried to open a dialog with you on this issue several times,
> > > but when I got no reply, I had to remove PGXLOG. If we had continued
> > > discussion, we
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Ya know, I'm sitting back and reading this, and other threads, and
> assimilating what is being bantered about, and start to think that
> its time to cut back on the gatekeepers ...
On the contrary, the quality of code accepted into a DBMS is reall
Marc G. Fournier wrote:
> > However, if you don't accept voting as a valid way to determine if a
> > patch is acceptible, what method do you suggest? I don't think we want
> > to go down the road of saying that you can't vote "no" on a feature
> > addition.
> >
> > We just rejected a patch today
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> You don't :vote: on stuff like this ...
Why not, exactly?
I wasn't aware that any of core had a non-vetoable right to apply
any patch we liked regardless of the number and strength of the
objections. AFAIK, we resolve differences of opinion by di
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I had a thought about what to do with the ECPG grammar-too-big problem:
>> rather than depending on a beta release of bison, we could attack the
>> problem directly by omitting some of the backend grammar from what ECPG
>> supports.
>
Hi Guys,
I'm heading off on a 5 week European trip tommorrow, so I'm not going to be
around until the 31st oct.
I hope there'll be a nice new release version of Postgres I can upgrade to
when I get back!
Chris
---(end of broadcast)---
TIP 5: Hav
I have updated /HISTORY for 7.3beta2. Looking at the open items list, I
think we are ready for beta2 now.
---
P O S T G R E S Q L
7 . 3 O P E NI T E M S
Curre
Sean Chittenden <[EMAIL PROTECTED]> writes:
> I'm thinking about changing this from a beta port to a -devel port
> that I'll periodically update with snapshots. I'll turn on -O6 for
> the -devel port and -O2 for production for now. If I don't hear of
> any random bogons in the code I'll see if
On 20 Sep 2002 at 18:41, Nigel J. Andrews wrote:
> On Fri, 20 Sep 2002, Shridhar Daithankar wrote:
>
> > In select test where approx. 15 rows where reported with query on index field,
> > mysql took 14 sec. and psotgresql took 17.5 sec. Not bad but other issues
> > eclipse the result..
>
> I
On Fri, Sep 20, 2002 at 01:12:17PM -0400, Bruce Momjian wrote:
>
> Tom has fixed it. Sorry I didn't test earlier.
Thanks.
> Neil Conway wrote:
> > It seems the 'numeric' and 'int8' tests are failing in CVS HEAD. The
> > culprit seems to be the recent to_char() change made by Karel, but I
> >
On Fri, Sep 20, 2002 at 09:24:00PM +0200, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > test=# select to_char(0,'FM9.9');
> > to_char
> > -
> > 0.
> > (1 row)
> >
> > test=# select to_char(1,'FM9.9');
> > to_char
> > -
> > 1.
> > (1 row)
>
> I find this highly bizzare. T
Tom Lane kirjutas P, 22.09.2002 kell 18:56:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> >> Another interesting case is multiple inheritance.
> >>
> >> create table p1 (f1 int);
> >> create table p2 (f1 int);
> >> create table c () inherits(p1, p2);
> >>
> >> drop ONLY column p1.f1;
> >> drop
33 matches
Mail list logo
