Sure. I didn't know there was a Debian start script. Because we
frequently keep up with the latest changes in postgres (which we
regularly use), I always build postgres from source. But that would be
a perfectly acceptable solution.
-tfo
On Aug 27, 2004, at 12:45 AM, Peter Eisentraut wrote:
setting reply-to to ppa-dev since I am pretty sure thats the list this
was meant for :-)
Chris, I don't have strong feelings one way or the other, but you do
have the option to vacuum full, so it could lock the table...
Robert Treat
On Thu, 2004-08-26 at 21:16, Christopher Kings-Lynne wrote:
The above error refers to a btree index, correct? Do/will a REINDEX fix
that, or do I have to physically DROP/CREATE the INDEX?
This is a 7.4 database, if that matters ...
Thanks ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]
Just so you know --- core has agreed that it's about time for beta2.
If you've got any must fix issues, please get 'em in over the weekend.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Marc G. Fournier [EMAIL PROTECTED] writes:
The above error refers to a btree index, correct? Do/will a REINDEX fix
that, or do I have to physically DROP/CREATE the INDEX?
REINDEX should fix it --- but how did it get that way?
regards, tom lane
On Fri, 27 Aug 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
The above error refers to a btree index, correct? Do/will a REINDEX fix
that, or do I have to physically DROP/CREATE the INDEX?
REINDEX should fix it --- but how did it get that way?
For lack of a better way of saying
Just so you know --- core has agreed that it's about time for beta2.
If you've got any must fix issues, please get 'em in over
the weekend.
The kill(0) patch from Dave for win32 is much needed (assuming it fixes
the issue. Unfortunatly Ive been swamped the past couple of weeks and
not able to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I was reading this two articles:
http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_beaverton.html
http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html
and I'm wondering if is a good idea apply a similar process to
Magnus Hagander [EMAIL PROTECTED] writes:
The kill(0) patch from Dave for win32 is much needed (assuming it fixes
the issue. Unfortunatly Ive been swamped the past couple of weeks and
not able to do much pg). I don't see it on the unapplied patches list,
but it's a trivial patch so it
-Original Message-
From: [EMAIL PROTECTED] on behalf of Magnus Hagander
Sent: Fri 8/27/2004 7:17 PM
To: Tom Lane; [EMAIL PROTECTED]
Subject: Re: [HACKERS] FYI: 8.0beta2 on Monday
Just so you know --- core has agreed that it's about time for beta2.
If you've got any must fix issues,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
| Just so you know --- core has agreed that it's about time for beta2.
| If you've got any must fix issues, please get 'em in over the weekend.
|
Are you going to insert the SetQuerySnapshot between conmmands in a plpgsql
function ?
Bruce Momjian [EMAIL PROTECTED] writes:
I am still seeing random regression test failures on my SMP BSD/OS
machine. It basically happens when doing 'gmake check'.
I have tried running repeated tests and can't get it to reproduce, but
when checking patches it has happened perhaps once a week
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was looking through the code of psql and had a few questions:
1. Do we want to use quote_ident on object names? Ideally, column
names with a space in them, for example, should be surrounded by
double quotes.
2. There is a disconnect between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 25 August 2004 02:15 pm, [EMAIL PROTECTED] wrote:
This is a first pass on a simple shared memory variable system for
PostgreSQL. I would appriciate anyone interested in this functionality to
rip it apart.
It basically adds this
On Fri, 27 Aug 2004, Greg Sabino Mullane wrote:
3. I'd like to rearrange the ORDER BY on some objects to show
user-created objects before system ones. Currently, if I create
a new function and do a \df, I have to wade through all the
system functions in the pg_catalog schema before seeing
At 03:25 AM 28/08/2004, Tom Lane wrote:
If you've got any must fix issues, please get 'em in over the weekend.
Is the 'magic_tablespace' variable going to be there?
Philip Warner| __---_
Albatross
Philip Warner [EMAIL PROTECTED] writes:
At 03:25 AM 28/08/2004, Tom Lane wrote:
If you've got any must fix issues, please get 'em in over the weekend.
Is the 'magic_tablespace' variable going to be there?
Likely not :-( ... I've just found about three issues I need to fix,
plus there's the
Marc G. Fournier [EMAIL PROTECTED] writes:
If you have stuff on your list 'to fix', do you want to put off beta2 a
few extra days, so that its that much cleaner for testers? Say, put it to
Wednesday so that you aren't sapping your weekend time?
[ shrug... ] There will always be stuff on my
I don't see how this is different from CREATE TABLE shared_variables
(name
VARCHAR PRIMARY KEY, value VARCHAR) and
inserting/updating/deleting/selecting from that. Perhaps these are
per-session shared variables? IN which case, what is the utility if
sharing
them across shared memory?
-
On Fri, 27 Aug 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
If you have stuff on your list 'to fix', do you want to put off beta2 a
few extra days, so that its that much cleaner for testers? Say, put it to
Wednesday so that you aren't sapping your weekend time?
[ shrug... ]
20 matches
Mail list logo
