Horton

Thread

  1. Postgres Future?

    Adriaan Joubert <a.joubert@albourne.com> — 1999-02-22T13:01:08Z

    Hi,

	I'vew been using Postgres since version 6.0, so for a considerable
period of time now. I have written quite a lot of code for postgres and
would be very reluctant to move to another database. Unfortunately quite
a few view-related queries are broken in 6.3.4 and I would like to
upgrade.

I do have a question about the future of Postgres on Digital Alpha (we
use almost exclusively DEC machines), as I have not managed to get any
of the 6.4.* versions to compile or run on DEC Alpha. I downloaded the
newest snapshot, managed to get it compiled and it failed all except 8
regression tests. I assume that has a lot to do with the Alphas being
64bit machines. Are there any plans to continue to support Alpha's, or
should I give up and look for an alternative?

I would be happy to compile snapshots and I can fix simple syntax bugs
etc to help to get postgres running on Alphas again, but I cannot get it
fixed by myself (I've tried and just got lost in the code). 

Cheers,

Adriaan

  2. Re: [GENERAL] Postgres Future?

    Bruce Momjian <maillist@candle.pha.pa.us> — 1999-02-22T16:50:43Z

    > Hi,
> 
> 	I'vew been using Postgres since version 6.0, so for a considerable
> period of time now. I have written quite a lot of code for postgres and
> would be very reluctant to move to another database. Unfortunately quite
> a few view-related queries are broken in 6.3.4 and I would like to
> upgrade.
> 
> I do have a question about the future of Postgres on Digital Alpha (we
> use almost exclusively DEC machines), as I have not managed to get any
> of the 6.4.* versions to compile or run on DEC Alpha. I downloaded the
> newest snapshot, managed to get it compiled and it failed all except 8
> regression tests. I assume that has a lot to do with the Alphas being
> 64bit machines. Are there any plans to continue to support Alpha's, or
> should I give up and look for an alternative?
> 
> I would be happy to compile snapshots and I can fix simple syntax bugs
> etc to help to get postgres running on Alphas again, but I cannot get it
> fixed by myself (I've tried and just got lost in the code). 

Seems we manage to mess up the 64-bit Alpha platform fairly regularly,
but don't have enough people testing the betas to put out a good final
release that works on alpha 100% of the time.

We basically need someone on Alpha involved in the beta process, when
that starts, who can run tests and show backtraces of the problems.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

  3. Re: [GENERAL] Postgres Future?

    Marc G. Fournier <scrappy@hub.org> — 1999-02-22T17:23:10Z

    On Mon, 22 Feb 1999, Adriaan Joubert wrote:

> Hi,
> 
> 	I'vew been using Postgres since version 6.0, so for a considerable
> period of time now. I have written quite a lot of code for postgres and
> would be very reluctant to move to another database. Unfortunately quite
> a few view-related queries are broken in 6.3.4 and I would like to
> upgrade.
> 
> I do have a question about the future of Postgres on Digital Alpha (we
> use almost exclusively DEC machines), as I have not managed to get any
> of the 6.4.* versions to compile or run on DEC Alpha. I downloaded the
> newest snapshot, managed to get it compiled and it failed all except 8
> regression tests. I assume that has a lot to do with the Alphas being
> 64bit machines. Are there any plans to continue to support Alpha's, or
> should I give up and look for an alternative?

There are no plans on discontinuing any of the ports that we have...the
problem is more availability of testers for them.  If you find problems
wtih any existing port of the server, please post a detailed report to
pgsql-ports@postgresql.org, if its a released version of PostgreSQL.  If
you are playing with the snapshots, post it directly to
pgsql-hackers@postgresql.org, since it might be something that we *just*
broken fixing somethign else...

We have a 1 month BETA period before a release, where we hope that those
that care about the various ports will take the time to test and run
regression tests...unfortunately, for those using it in a production
environment, this isn't always possible, so some ports get less attention
then others ;(

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org

  4. combining contents of two fields into a new field?

    William J. Stotts <wstotts@sonitrol.net> — 1999-02-22T17:38:58Z

    Hi folks,

Please excuse this question for it shows my ignorance;-)

I need to combine the contents of three different fields into a single
field. I understand how to perform an update on a field with the contents
of another field via a query like:
 UPDATE dice_data SET dice_new_phone = dice_prefix

I need to update this field with a concatenation of three fields actually.
What I am ignorant of is how to perform such an update. WOuld someone
kindly guide me in how to perform such an update?

Thanks in advance8-)

Bill Stotts

ps-please reply to me directly as well as the mailing list.


**************************************************************************
Bill Stotts                          |  Voice: 860-616-7535
wstotts@sonitrol.net                 |    Fax: 860-616-7589 
Sonitrol Communications Corp.        |
                                     |   
_SONITROL_ Expect the best...        |  Where do you want to GO tomorrow?
**************************************************************************

  5. Re: [GENERAL] combining contents of two fields into a new field?

    Ross Reedstrom <reedstrm@rice.edu> — 1999-02-22T18:23:41Z

    With the || concationation operator, as so:

UPDATE dice_data SET dice_new_phone = dice_prefix || dice_phone

Note, however, that for some reason you must add axplicit parens for
multiple concats:

UPDATE dice_data SET dice_new_phone = dice_prefix || dice_phone ||
dice_suffix

won't work (yet!), but:

UPDATE dice_data SET dice_new_phone = (dice_prefix || dice_phone)||
dice_suffix

should.

William J. Stotts wrote:
> 
> Hi folks,
> 
> Please excuse this question for it shows my ignorance;-)
> 
> I need to combine the contents of three different fields into a single
> field. I understand how to perform an update on a field with the contents
> of another field via a query like:
>  UPDATE dice_data SET dice_new_phone = dice_prefix
> 
> I need to update this field with a concatenation of three fields actually.
> What I am ignorant of is how to perform such an update. WOuld someone
> kindly guide me in how to perform such an update?
> 
> Thanks in advance8-)
> 
> Bill Stotts
> 
> ps-please reply to me directly as well as the mailing list.
> 
> **************************************************************************
> Bill Stotts                          |  Voice: 860-616-7535
> wstotts@sonitrol.net                 |    Fax: 860-616-7589
> Sonitrol Communications Corp.        |
>                                      |
> _SONITROL_ Expect the best...        |  Where do you want to GO tomorrow?
> **************************************************************************

-- 
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> 
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St.,  Houston, TX 77005

  6. Re: [GENERAL] combining contents of two fields into a new field?

    Jeff Hoffmann <jeff@remapcorp.com> — 1999-02-22T18:40:01Z

    "William J. Stotts" wrote:
> 
> Hi folks,
> 
> Please excuse this question for it shows my ignorance;-)
> 
> I need to combine the contents of three different fields into a single
> field. I understand how to perform an update on a field with the contents
> of another field via a query like:
>  UPDATE dice_data SET dice_new_phone = dice_prefix
> 
> I need to update this field with a concatenation of three fields actually.
> What I am ignorant of is how to perform such an update. WOuld someone
> kindly guide me in how to perform such an update?
> 

if the fields are character data, you'd want to use the concatenate
operator "||".  the last i checked, you can't string a bunch of fields
together, so more than two fields is a PITA (you have to use a bunch of
parentheses to group things together).  there was talk of changing this,
but i forget what happened to it.

for example a phone number might be something like this:

update my_data set new_phone = (('(' || area_code) || ') ') || ((prefix
|| '-') || number);

(i hope i got the parentheses right, and i hope this helps.)

jeff