Thread: add space to expand database ?

add space to expand database ?

From
Andreas Schmitz
Date:
Hello *,

I have a little problem with a database that is growing drastically. I am
getting short on diskspace within $PGDATA. Is there a way to use $PGDATA2 in
addition to $PGDATA with the same database ?

regards

-andreas


--
Andreas Schmitz - Phone +49 201 8501 318
Cityweb-Technik-Service-Gesellschaft mbH
Friedrichstr. 12 - Fax +49 201 8501 104
45128 Essen - email a.schmitz@cityweb.de


any known issues with 7.3?

From
Timothy D McKernan
Date:
My company and one of our clients have been using 7.3 internally since
it was released last month.  It has been performing very well, we're
nearly finished testing it in our development and test environments.  So
it's meeting our expectations with both performance and
deployment/admin'ing.

Before we push it out into our production environment I wanted to make
one last check with regards to bugs - is anybody aware of any bugs that
have popped up in 7.3?  I haven't seen any unexpected issues on the
mailing lists but I wanted to make sure I haven't missed anything.

Thanks,
Tim


Re: any known issues with 7.3?

From
"David F. Skoll"
Date:
On Mon, 23 Dec 2002, Timothy D McKernan wrote:

> Before we push it out into our production environment I wanted to make
> one last check with regards to bugs - is anybody aware of any bugs that
> have popped up in 7.3?  I haven't seen any unexpected issues on the
> mailing lists but I wanted to make sure I haven't missed anything.

Not a bug, but something that bit me:  Whereas 7.2.x accepts the expression
"current_date()", 7.3 insists on "current_date" without the parentheses.
It was probably an error on my part originally; the parser seems
to have been tightened up.  You might want to test all your queries to
ensure the syntax is correct.

Other than that, 7.3 has worked fine for me in my tests.

--
David.

Re: any known issues with 7.3?

From
Bruce Momjian
Date:
We just released 7.3.1, so I would use that.  It has minor fixes from 7.3.

---------------------------------------------------------------------------

Timothy D McKernan wrote:
> My company and one of our clients have been using 7.3 internally since
> it was released last month.  It has been performing very well, we're
> nearly finished testing it in our development and test environments.  So
> it's meeting our expectations with both performance and
> deployment/admin'ing.
>
> Before we push it out into our production environment I wanted to make
> one last check with regards to bugs - is anybody aware of any bugs that
> have popped up in 7.3?  I haven't seen any unexpected issues on the
> mailing lists but I wanted to make sure I haven't missed anything.
>
> Thanks,
> Tim
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Re: add space to expand database ?

From
Tom Lane
Date:
Andreas Schmitz <a.schmitz@cityweb.de> writes:
> I have a little problem with a database that is growing drastically. I am
> getting short on diskspace within $PGDATA. Is there a way to use $PGDATA2 in
> addition to $PGDATA with the same database ?

There's no really practical way to do that at the moment within
Postgres.  I'd recommend looking into OS-level facilities for spreading
a filesystem over multiple physical volumes --- depending on your
platform you might be able to do it with LVM, software RAID, etc.

            regards, tom lane

Re: add space to expand database ?

From
Andreas Schmitz
Date:
On Monday 23 December 2002 18:54, Tom Lane wrote:
> Andreas Schmitz <a.schmitz@cityweb.de> writes:
> > I have a little problem with a database that is growing drastically. I am
> > getting short on diskspace within $PGDATA. Is there a way to use $PGDATA2
> > in addition to $PGDATA with the same database ?
>
> There's no really practical way to do that at the moment within
> Postgres.  I'd recommend looking into OS-level facilities for spreading
> a filesystem over multiple physical volumes --- depending on your
> platform you might be able to do it with LVM, software RAID, etc.
>
>             regards, tom lane

Hi Tom,

thanks a lot for the answer. I considered using the raid functionality. My
problem is that I will loose days of work when I have to stop now. A $PGDATA2
ist known to the databaseserver. However, are there any plans for postgresql
to implement this feature ?

kind regards

-andreas

--
Andreas Schmitz - Phone +49 201 8501 318
Cityweb-Technik-Service-Gesellschaft mbH
Friedrichstr. 12 - Fax +49 201 8501 104
45128 Essen - email a.schmitz@cityweb.de


Re: add space to expand database ?

From
Tom Lane
Date:
Andreas Schmitz <a.schmitz@cityweb.de> writes:
> However, are there any plans for postgresql
> to implement this feature ?

Tablespaces are on the TODO list, and may actually get done for 7.4.
But that isn't going to help you today...

            regards, tom lane

Re: any known issues with 7.3?

From
"Rajesh Kumar Mallah."
Date:
Third party software that use limit a,b  syntax
*wont* work unless u have the source code and time
to change all "limit a,b" to "limit a offset b" syntax.

this is one issue that forced me to use 7.2.x for one
of my tickect systems.


regds
mallah.


On Monday 23 December 2002 09:01 pm, Timothy D McKernan wrote:
> My company and one of our clients have been using 7.3 internally since
> it was released last month.  It has been performing very well, we're
> nearly finished testing it in our development and test environments.  So
> it's meeting our expectations with both performance and
> deployment/admin'ing.
>
> Before we push it out into our production environment I wanted to make
> one last check with regards to bugs - is anybody aware of any bugs that
> have popped up in 7.3?  I haven't seen any unexpected issues on the
> mailing lists but I wanted to make sure I haven't missed anything.
>
> Thanks,
> Tim
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)

Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.



Re: any known issues with 7.3?

From
Jeff Boes
Date:
On Mon, 23 Dec 2002 10:41:31 -0500, Timothy D McKernan wrote:

> Before we push it out into our production environment I wanted to make
> one last check with regards to bugs - is anybody aware of any bugs that
> have popped up in 7.3?  I haven't seen any unexpected issues on the
> mailing lists but I wanted to make sure I haven't missed anything.
>

Probably too late for the OP, but I've noted here before that the current
version of DBD::Pg (Perl driver used by the DBI) doesn't work under 7.3
(the DBD::Pg code uses fields from an interal pg_* table that are no
longer supported).

--
Jeff Boes                                      vox 616.226.9550 ext 24
Database Engineer                                     fax 616.349.9076
Nexcerpt, Inc.                                 http://www.nexcerpt.com
           ...Nexcerpt... Extend your Expertise

Re: any known issues with 7.3?

From
Bruce Momjian
Date:
Would you grab the CVS and give it a try.  I want to put out a new
release shortly anyway.

---------------------------------------------------------------------------

Jeff Boes wrote:
> On Mon, 23 Dec 2002 10:41:31 -0500, Timothy D McKernan wrote:
>
> > Before we push it out into our production environment I wanted to make
> > one last check with regards to bugs - is anybody aware of any bugs that
> > have popped up in 7.3?  I haven't seen any unexpected issues on the
> > mailing lists but I wanted to make sure I haven't missed anything.
> >
>
> Probably too late for the OP, but I've noted here before that the current
> version of DBD::Pg (Perl driver used by the DBI) doesn't work under 7.3
> (the DBD::Pg code uses fields from an interal pg_* table that are no
> longer supported).
>
> --
> Jeff Boes                                      vox 616.226.9550 ext 24
> Database Engineer                                     fax 616.349.9076
> Nexcerpt, Inc.                                 http://www.nexcerpt.com
>            ...Nexcerpt... Extend your Expertise
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073