On Tue, Sep 14, 2004 at 08:13:24AM -0400, Matthew T. O'Connor wrote:
> On Tue, 2004-09-14 at 00:46, Chester Kustarz wrote:
> > On Mon, 13 Sep 2004, Matthew T. O'Connor wrote:
> > > I backed up the entire data directory, and did a pg_resetxlog, but that
> > > didn't help. I found the specific row t
On Tue, 14 Sep 2004, Christian Sell wrote:
> Hello,
>
> I am running into a problem with PGs case sensitivity with regard to column and
> table names. I am using program components that require the object names
> returned from database metadata queries to be in uppercase. Therefore, I am
> forced
"Michael Paesold" <[EMAIL PROTECTED]> writes:
> I though the postgres behaviour of rolling back the whole transaction was
> standard?
Not really.
> If that is not the case, I don't understand why core seems to be
> against a mode (GUC), where an implicit savepoint is generated before each
> state
On Tue, 14 Sep 2004, Oliver Elphick wrote:
> The fault is with your program components that are insisting on upper
> case rather than accepting either case.
In defence of this unknown component, the sql specifications says that
identifiers should be upper cased where pg do lower case.
I would w
Stephan Szabo <[EMAIL PROTECTED]> writes:
> ... There's been talk about supporting a
> mode which case folds the other direction. In general, however, mixing
> quoted and unquoted names is dangerous in all complient databases, because
> in none would "Bla" and bla or BLA be the same name.
We have
On Tue, 14 Sep 2004, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > ... There's been talk about supporting a
> > mode which case folds the other direction. In general, however, mixing
> > quoted and unquoted names is dangerous in all complient databases, because
> > in none would
Tom Lane wrote:
> I wonder though whether we could offer some tweaking on client side.
> For instance consider the JDBC driver's getMetaData operations.
> You could imagine a JDBC driver mode that would smash all returned
> identifiers to upper case.
Then again, JDBC applications can query
Databa
> You could take a look at contrib/dblink because
> apparantly you can open
>a connection to another (and probably the same)
> DB, and then write
> your logging information that way (ie within a
> function or session).
> Anything you do using the dblink will not be rolled
> back.
Superb! It
On Wed, Sep 08, 2004 at 03:12:29 +,
Randy Yates <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Ben) writes:
>
> > Well, R/W doesn't make much sense for TCP incoming/outgoing SYN
> > packets make more sense, and if the database is located outside the
> > firewall, you really only need to
I have moved a DB from 7.4.3 to 8.0.0b2 for testing and am
experiencing some
problems with the void type within pl functions. I am calling a
function which
returns a void from within another function and have defined a
variable of type
void to catch
Once I've gotten multiple values back from a plpgsql function,
how do I actually reference those values in another plpgsql
function? I've tried several syntaxes and keep getting errors.
Various attempts are below.
Thanks.
On 2004.09.08 15:59 Joe Conway wrote:
Ah yes, that works too. For the record
> "SW" == Shane Wright writes:
SW> But, we have now taken the plunge and I'm in a position to do some
SW> benchmarking to actually get some data. Basically I was wondering if
SW> anyone else had any particular recommendations (or requests) about the
SW> most useful kinds of benchmarks to do.
> "CP" == Collin Peters <[EMAIL PROTECTED]> writes:
CP> I have thought of the following situations:
CP> -Simply track all the changes you made to the development database and
CP> make the same changes to the release database
CP> -Back up the release database... overwrite it with the developmen
What the hell? I got this message but when I check my IP in sorbs it says it's
not there. Is something wrong with svr1.postgresql.org?
Mail Delivery System <[EMAIL PROTECTED]> writes:
> This message was created automatically by mail delivery software (Exim).
>
> A message that you sent could
On Tue, 2004-09-14 at 10:28, Vivek Khera wrote:
> > "SW" == Shane Wright writes:
>
> SW> But, we have now taken the plunge and I'm in a position to do some
> SW> benchmarking to actually get some data. Basically I was wondering if
> SW> anyone else had any particular recommendations (or requ
Hi,
I have a question about alter a column's type in a postgreSQL table.
For example, I have 10, 000 records in a table name "test", I'd like to
change column "machineID" type from integer to varchar. I am looking for
something like:
alter table test alter column machineID ... ... varchar
Thanks
Hello,
You can not currently change the data type with alter table.
J
Ying Lu wrote:
Hi,
I have a question about alter a column's type in a postgreSQL table.
For example, I have 10, 000 records in a table name "test", I'd like to
change column "machineID" type from integer to varchar. I am looking
Hi,
If you're using 7.4 or below (I'm not sure if 7.5 is able to do this),
you'll end up writing the data first to a temporary table, as in (for
example):
SELECT * INTO TEMPORARY MyTable
FROM yourtable;
DROP TABLE yourtable;
CREATE TABLE yourtable (
/* with varchar stuff */
) WITH OIDS;
IN
On Tue, 14 Sep 2004 13:33:32 -0700, Joshua D. Drake
<[EMAIL PROTECTED]> wrote:
> You can not currently change the data type with alter table.
Are there any plans to add this functionality?
What's the best workaround? Add a new column, copy data from old
column to new column, drop old column?
-
Can somebody clue me in on this? I've been working on this for nearly a
week now and it's driving me bunkers.
I am using PostGIS/Mapserver and trying to get a simple demo running
with just one PostGIS layer. My layer is never drawn and the best I can
tell is the results from this transaction (no
On Tue, Sep 14, 2004 at 03:53:07PM -0500, Greg Donald wrote:
> On Tue, 14 Sep 2004 13:33:32 -0700, Joshua D. Drake
> <[EMAIL PROTECTED]> wrote:
> > You can not currently change the data type with alter table.
>
> Are there any plans to add this functionality?
It's in 8.0 already.
--
Alvaro Herr
I have a small training database: sql_tutorial. It works fine but the spacing
between the output lines is too much. This is the way it looks when I copy
and paste from the Konsole to this email:
sql_tutorial=> SELECT prod_name FROM Products;
prod_nam
Currently, what I did is like
. alter table test add column machineIDnew varchar;
. update test set machineIDnew = machineID;
. alter table test rename machineIDnew to machineID;
. vacuum full table;
If better ways, please let me know.
Thanks a lot,
Greg Donald wrote:
On Tue, 14 Sep 2004 13:33:32 -
On Tue, Sep 14, 2004 at 01:33:32PM -0700, Joshua D. Drake wrote:
> You can not currently change the data type with alter table.
... but you can add a new column with the desired type, UPDATE it with
the transformed data, and the DROP the old column.
> Ying Lu wrote:
> >I have a question about a
The spacing in Konsole is directly related to the wrapping that it's
doing based on the size of the prod_name field (I.e., length in terms
of characters).
You can alter the format settings of psql. See:
http://www.postgresql.org/docs/7.4/static/app-psql.html
-tfo
On Sep 14, 2004, at 4:05 PM, J
Title: RE: [GENERAL] Spacing in output
What is the field size of prod_name? You could use SUBSTR(prod_name,1,xx) where xx is the max number of characters you want to see.
Duane
-Original Message-
From: Jerome Lyles [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 14, 2004 2:06 P
I'm thinking of getting this book and was wondering if anyone had
anything bad (or good) to say about it? More than that I'd really
like to know what version of Postgres it covers, the sample pages
don't seem to say.
http://tinyurl.com/5xtpp
TIA..
--
Greg Donald
http://destiney.com/
--
On Tue, Sep 14, 2004 at 11:05:46AM -1000, Jerome Lyles wrote:
> I have a small training database: sql_tutorial. It works fine but the spacing
> between the output lines is too much. This is the way it looks when I copy
> and paste from the Konsole to this email:
>
> sql_tutorial=> SELECT prod_
On Tue, Sep 14, 2004 at 11:11:38AM -0700, Jeffrey W. Baker wrote:
> procs ---memory-- ---swap-- -io --system-- cpu
> r b swpd free buff cache si sobibo incs us sy id wa
> 3 0216 13852 39656 773972400 820 2664 2868 2557 1
I used this book as my intro and my guide in my first few months running
postgresql
I thought it was super informative...had lots of real usable infoand
I still occasionally refer to it...
Jeff
Greg Donald wrote:
I'm thinking of getting this book and was wondering if anyone had
anything
Title: RE: [GENERAL] postgres book
I like the book. It covers up to 7.2 but don't let that bother you it still has plenty of appropriate information crammed inside.
Duane
-Original Message-
From: Greg Donald [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 14, 2004 2:37 PM
To: p
On Tue, 2004-09-14 at 14:45, Jim C. Nasby wrote:
> On Tue, Sep 14, 2004 at 11:11:38AM -0700, Jeffrey W. Baker wrote:
> > procs ---memory-- ---swap-- -io --system-- cpu
> > r b swpd free buff cache si sobibo incs us sy id wa
> > 3 0216
32 matches
Mail list logo
