pgsql.novice
  Home FAQ Contact Sign in
pgsql.novice only
 
Advanced search
July 2008
motuwethfrsasuw
 123456 27
78910111213 28
14151617181920 29
21222324252627 30
28293031    31
2008
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2008 2007 2006  
total
pgsql.novice Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  CANNOT CREATE A TABLESPACE         


Author: JORGE MALDONADO
Date: Jul 24, 2008 10:06

I am trying to create a new Tablespace without success. I am using
PostgreSQL 8.3 and pgAdmin III v1.8.2 in a Windows XP Professional
environment with the following steps:

1. I create an empty directory called c:\pgppdata using Windows Explorer.
2. I right click on Tablespaces in pgAdmin III interface and select New
Tablespace
3. I give it the name e_restdelivery
4. In location I type c:\pgappdata (the directory created in step 1)
5. In owner I select postgres and click the OK button.
6. I get a message saying *** ERROR: could not set permissions on directory
"c:/pgappdata": Permissiond denied ***

Note that the slash in the message is not the same I use in step 1; I have
used both in the first step with the same result.

Please advice.

With respect,
Jorge Maldonado

I am trying to create a new Tablespace without success. I am using PostgreSQL 8.3 and pgAdmin III v1.8.2 in a Windows XP Professional environment with the following steps:
 
1. I create an empty directory ...
Show full article (1.58Kb)
1 Comment
  Re: Character set conversion         


Author: Tom Lane
Date: Jul 21, 2008 07:16

Bastiaan Olij writes:
> I read in the documentation about the 'Create conversion' command
> writing a function to do the conversion job. Is this the best way
> forward or are there better ways to attempt this? Is there any sample
> code available for implementing such a conversion? I don't want to
> reinvent the wheel here...

Look into the PG source code under
src/backend/utils/mb/conversion_procs.

While an add-on conversion procedure isn't too hard, I don't think
there's any way to define a whole new encoding without modifying the
source code --- the encodings are listed in some hard-coded tables
in the C code rather than being defined by a system catalog. It
wouldn't be too hard if you don't mind running a custom Postgres
build; but if you do, then the best answer might be to cannibalize
one of the existing encoding names and just replace its conversion
procedures.

regards, tom lane
Show full article (1.08Kb)
1 Comment