"Dai, Tino" writes:
> After many days of googling and referring to different web pages about
> performance, I'm
> turning to this list for help. We have a third party application that is
> running on 8.1.11 and the
> vendor has told us not to upgrade the database to 8.2.
8.2 was released in 20
Szymon Guz wrote:
> 2010/3/19 Tom Lane
>
> > Szymon Guz writes:
> > > You won't have to change the parameters in the function definition,
> > instead
> > > you can use the RENAME clause:
> >
> > > CREATE OR REPLACE FUNCTION add_user(user varchar(20), password
> > varchar(20) )
> > > RETURNS VOID
On Mon, Mar 22, 2010 at 3:58 PM, Dai, Tino wrote:
> After many days of googling and referring to different web pages about
> performance, I'm
> turning to this list for help. We have a third party application that is
> running on 8.1.11 and the
> vendor has told us not to upgrade the database to
After many days of googling and referring to different web pages about
performance, I'm
turning to this list for help. We have a third party application that is
running on 8.1.11 and the
vendor has told us not to upgrade the database to 8.2.
I have gone with the default values in postgresql.con
On Mon, Mar 22, 2010 at 2:48 AM, Iñigo Martinez Lasala
wrote:
> Hi everybody.
>
>
>
> I have a doubt about how postgres deal with bad encoded characters into
> database.
>
> We have several gforge application. They are using postgres as database.
>
> If we export a database and import again, we ha
Hi,
I agree with this postgres policy, but what I don’t is that you can
INSERT them via application. That is, no bad characters should be
inserted into database. The check should be made for both import and
insert procedures so no bad chars would appear into database.
Could you please tell
2010/3/19 Antoine POPINEAU
> Hi,
>
> I am developping a Java application, and using a PostgreSQL backend
> database. Theorically, there might be lots of users, each with potentially
> different permissions over the different tables.
>
> I could add those user to the database with a classic CREATE
Lots there, let's break it down individually:
On Mon, Mar 22, 2010 at 6:38 AM, blast wrote:
>
> Hi all,
>
> I need to backup and restore a DB.
> In this particular case the data in the database is not important (strange
> hum...) but only the schema to put new data...
>
> I m thinking use the p
Hi all,
I need to backup and restore a DB.
In this particular case the data in the database is not important (strange
hum...) but only the schema to put new data...
I m thinking use the pg_dump:
pg_dump -c -C -s schema > file.out
With this i have in file.out the schema, correct?
So, to restor
Hi
Further to David Jantzen's post of 3/16/2010.
We have decided to try to upgrade the database software from our old custom
8.3.7 instance to the std upstream 8.3.10 version.
We have no hash indexes on interval types; we therefore anticipate that the
migration will be a shutdown of the old ins
Hi,
I am developping a Java application, and using a PostgreSQL backend
database. Theorically, there might be lots of users, each with
potentially different permissions over the different tables.
I could add those user to the database with a classic CREATE USER, but
that doesn't seem efficie
Try
function add_user(_user varchar(20), _password varchar(20))
INSERT INTO my_users(user, password) VALUES (_user, _password);
-Mensaje original-
De: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org]
En nombre de Julius Tuskenis
Enviado el: viernes, 19 de mar
On Sun, 2010-03-21 at 21:11 +0100, Yazid Levasseur wrote:
> r...@myservercrashedoncopy :/usr/lib/postgresql/8.4/bin# pg_resetxlog
> -f /var/lib/postgresql/8.4/main
> -bash: pg_resetxlog: command not found
Either ./pg_resetxlog -f ... ,
or /usr/lib/postgresql/8.4/bin/pg_resetxlog -f Another w
Hi everybody.
I have a doubt about how postgres deal with bad encoded characters into
database.
We have several gforge application. They are using postgres as database.
If we export a database and import again, we have to deal with several bad
encoded chars. These bad chars always come from co
14 matches
Mail list logo
