When restoring from a pg_dumpall file, is it best to delete the contents
of the data folder, run intitdb to recreate it, and then do the command
"psql -U postgres -f backupfile postgres"?
When I do the restore over top of what is in the data folder already,
there are many errors reported.
Thanks
Thanks for the confirmation of this. For now I'll continue to use the C
locale and I'll switch with 8.3.1.
Meetesh
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
I think this is a "must fix" bug for 8.3.1, anyone disagree?
Agreed.
It seems we should collect cases lik
"Tom Lane" <[EMAIL PROTECTED]> writes:
> I think this is a "must fix" bug for 8.3.1, anyone disagree?
Agreed.
It seems we should collect cases like this for the regression tests. The only
one I was aware of previously was the Turkish one.
--
Gregory Stark
EnterpriseDB http://www.e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 13 Mar 2008 12:04:27 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> Geoffrey <[EMAIL PROTECTED]> writes:
> > Joshua D. Drake wrote:
> >> I would avoid 8.3 without extensive testing. 8.2.6 is likely a
> >> better shot a minimizing one off incompat
Tom Lane wrote:
Geoffrey <[EMAIL PROTECTED]> writes:
Joshua D. Drake wrote:
I would avoid 8.3 without extensive testing. 8.2.6 is likely a better
shot a minimizing one off incompatibilities.
We are in a very similar situation in that we are looking to migrate
from 7.4 to 8.3. So seeing Scot
Geoffrey <[EMAIL PROTECTED]> writes:
> Joshua D. Drake wrote:
>> I would avoid 8.3 without extensive testing. 8.2.6 is likely a better
>> shot a minimizing one off incompatibilities.
> We are in a very similar situation in that we are looking to migrate
> from 7.4 to 8.3. So seeing Scott's and J
Meetesh Karia <[EMAIL PROTECTED]> writes:
> Additionally, here's what I get when I run your test below (my server
> encoding is UTF-8):
> ltefull=# create table x (r varchar(255) unique);
> NOTICE: CREATE TABLE / UNIQUE will create implicit index "x_r_key" for
> table "x"
> CREATE TABLE
> ltefu
Pietro <[EMAIL PROTECTED]> writes:
> It isn't so serious problem for me, only boring one, because each morning
> I must start server box and then manually restart posgresql server.
There must be something different between what you do manually and what
the init script does ... better take a close
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 12 Mar 2008 22:50:21 -0700
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
And if the OP is worried about running too new a version of pgsql,
8.2.6 is very mature. But if he's got 6 or more months until he goes
live, whic
Thanks to help from Sergey Benner, I was able to narrow the problem
down. When I first initialized the PG cluster, I used the following
command:
initdb -D d:/postgres/8.3/data -E UTF8 -U postgres
And that set my LC_COLLATE and LC_CTYPE values to 'English_United
States.1252'. 'en_US-UTF-8' w
double check pg_hba.conf
> From: [EMAIL PROTECTED]
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] LAN connection to server only after restart server
> Date: Thu, 13 Mar 2008 10:20:07 +0100
>
> Hi,
>
> I have strange behaviour on my LAN.
>
> Postgresql server is up and running, accepti
Thanks for your response Robert.
Unfortunately I don't think that will work (unless I'm misunderstanding
something).
I can't export using a client encoding of WIN1250 because I have true
UNICODE chars which can't be represented with it (I've tried and I get
the error below). Therefore, I ha
Hi,
I have strange behaviour on my LAN.
Postgresql server is up and running, accepting connection on default port.
Firewall is set well.
Connection from 'localhost' is OK.
Connection from another host on LAN is refused (sniffed with wireshark:
request ACK, response RST, ACK) and so application sh
13 matches
Mail list logo
