> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> I don't believe Bruce has yet made any effort to update the SGML
TL> release-notes file for 7.4. Instead look at the CVS-tip HISTORY file:
Definitely not since the 7.4b2 INSTALL docs refer to it being version
7.3.
--
=-=-=-=-=-=-=-=-=-=-=
> "SD" == Shridhar Daithankar <[EMAIL PROTECTED]> writes:
>> Reindexing a table takes an exclusive table lock. If I did it inside
>> a transaction, wouldn't it still take that lock and block out all
>> other access?
SD> Well, you donm't need to reindex as such. You can create a new index fro
On Tue, 2 Sep 2003, Bo Lorentsen wrote:
> On Tue, 2003-09-02 at 22:21, Bruno Wolff III wrote:
>
> > This will be a little easier than checking out a copy from CVS. However,
> > I think the HISTORY file has more detail in it.
> I think you are right, maybe a cvsview utility would help, regarding
>
On Tue, 2003-09-02 at 23:32, Tom Lane wrote:
> I don't believe Bruce has yet made any effort to update the SGML
> release-notes file for 7.4. Instead look at the CVS-tip HISTORY file:
> http://developer.postgresql.org/cvsweb.cgi/pgsql-server/HISTORY
Ok thanks, this is very usefull !
/BL
-
On Tue, 2003-09-02 at 22:21, Bruno Wolff III wrote:
> This will be a little easier than checking out a copy from CVS. However,
> I think the HISTORY file has more detail in it.
I think you are right, maybe a cvsview utility would help, regarding
this problem ? But a bugzilla tool, may also be nice
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Bo Lorentsen <[EMAIL PROTECTED]> wrote:
>> Are there a list of things that will be done in 7.4, or better a
>> development roadmap like the one the Mozilla folks are using ?
> For a quick look see the current version of the release notes on the web a
On 2 Sep 2003 at 9:36, Vivek Khera wrote:
> > "BL" == Bo Lorentsen <[EMAIL PROTECTED]> writes:
>
> BL> On Tue, 2003-09-02 at 04:08, Vivek Khera wrote:
> >> 3) Index bloat is apparently a bigger problem than I thought.
> BL> This does not sound too nice !
>
> No, like I said, I shaved 900Mb o
> "BL" == Bo Lorentsen <[EMAIL PROTECTED]> writes:
BL> On Tue, 2003-09-02 at 04:08, Vivek Khera wrote:
>> I use it in 24/7/365 system which is heavily written to and read
>> from. The drawbacks I have are:
BL> How depressing, may I ask that PG version you are using ?
Currently 7.2 in product
On 2 Sep 2003 at 12:25, Bo Lorentsen wrote:
> On Tue, 2003-09-02 at 11:55, Shridhar Daithankar wrote:
>
> > That's fixed in 7.4. Vacuum in 7.4 prevents index bloat as well. Couple with
> > autovacuum daemon or scheduled vacuums, things (hopefully) will be lot better
> > than earlier days..
> Ar
> These things are quite important when you have to convince your boss :-)
Convincing boss just say: "Caugh board or use postgresql".
Meaning of this is that you can't compare comercical or free ware.
Probably you want to use postgre because of its free, if this isn't case
why you won use oracle
On Sat, Aug 30, 2003 at 01:59:20PM +0200, Bo Lorentsen wrote:
> He likes to know about others using Postgres and simple replication (we
> need it in at 24/7 system), to know how postgres performs, and how
> stable it is regarding its data and the backup feature etc.
The replication system release
Lamar Owen wrote:
> Nitpik: that should be 24/7/52, since there aren't 365 weeks in a year.
Oh, great. It's just that 7*52 = 364. That leaves us with a full day to idle
and still honor the SLA, right?
Sorry, couldn't resist :)
cl.
---(end of broadcast)-
On Tue, 2003-09-02 at 11:55, Shridhar Daithankar wrote:
> That's fixed in 7.4. Vacuum in 7.4 prevents index bloat as well. Couple with
> autovacuum daemon or scheduled vacuums, things (hopefully) will be lot better
> than earlier days..
Are there a list of things that will be done in 7.4, or bet
On 2 Sep 2003 at 11:49, Bo Lorentsen wrote:
> > 3) Index bloat is apparently a bigger problem than I thought.
> This does not sound too nice !
That's fixed in 7.4. Vacuum in 7.4 prevents index bloat as well. Couple with
autovacuum daemon or scheduled vacuums, things (hopefully) will be lot better
On Tue, 2003-09-02 at 04:08, Vivek Khera wrote:
> I use it in 24/7/365 system which is heavily written to and read
> from. The drawbacks I have are:
How depressing, may I ask that PG version you are using ?
> 1) upgrade to major versions require dump/restore which is a
>significant amount of
On Monday 01 September 2003 22:08, Vivek Khera wrote:
> I use it in 24/7/365 system which is heavily written to and read
> from. The drawbacks I have are:
Nitpik: that should be 24/7/52, since there aren't 365 weeks in a year.
> 1) upgrade to major versions require dump/restore which is a
>s
> "BL" == Bo Lorentsen <[EMAIL PROTECTED]> writes:
BL> Hi ..
BL> He likes to know about others using Postgres and simple replication (we
BL> need it in at 24/7 system), to know how postgres performs, and how
BL> stable it is regarding its data and the backup feature etc.
I use it in 24/7/365
Oops! Jacob Hanson <[EMAIL PROTECTED]> was seen spray-painting on a wall:
> On Sat, 30 Aug 2003 16:18:14 +0200 (CEST), [EMAIL PROTECTED] (Peter
> Eisentraut) wrote:
>>many, but it's usually difficult to get customers to agree to this sort of
>>thing.
>
> Why is that?
Because:
1. What tools they
On Sat, 30 Aug 2003 16:18:14 +0200 (CEST), [EMAIL PROTECTED] (Peter
Eisentraut) wrote:
>many, but it's usually difficult to get customers to agree to this sort of
>thing.
Why is that?
---(end of broadcast)---
TIP 8: explain analyze is your friend
19 matches
Mail list logo
