See the pgupgrade utility in 6.4.*.
> Hi
>
> My guess would be to totally delete the data directory (~postgres/data)
> and put your old one in its place. As opposed to copying over it, which
> may leave the old (new old) stuff in the way.
>
> Terry
>
> On Tue, 9 Feb 1999, G. Anthony Reina wro
Hi
My guess would be to totally delete the data directory (~postgres/data)
and put your old one in its place. As opposed to copying over it, which
may leave the old (new old) stuff in the way.
Terry
On Tue, 9 Feb 1999, G. Anthony Reina wrote:
> I recently updated my OS to RedHat 5.2 with the
I recently updated my OS to RedHat 5.2 with the 2.2 Kernel. I was last
using Postgres 6.4.2 with my database. I re-installed Postgres 6.4.2
into the new operating system and tried to copy the contents of the
database directory over to the newly installed directory.
I am able to select and update
Hi Ken
As I recall it is a compile time option that can be changed to what ever
you need it to be.
Terry
On Mon, 8 Feb 1999, Ken Mort wrote:
> I was reading in the hackers list threads regarding workarounds
> to the 8k block limit.
> I have a number of polygon objects that are bigger than 8k.
I was reading in the hackers list threads regarding workarounds
to the 8k block limit.
I have a number of polygon objects that are bigger than 8k. Has a
workaround been done? The hackers thread seemed to indicate
that it would be in 6.3.2 but was delayed. Is there a fix in 6.4.x?
Regards,
Kenne
Hi, I have a table with 100 registers in Postgres with Linux RH5.1 and I
want to copy it to other Linux machine with Postgres, my question is may
be a little dummy: is there a command in Postgres that allows this copy or
I have to re-do the tables and write again the registers that I have in
the o
Wow, Marc is asking for help?
Try: ALTER USER user_name WITH PASSWORD new_password;
Never tried it myself,
-DEJ
> create user allows you to set a password for someone...how to
> you change
> that password after?
>
> update doesn't appear to work...
