[BUGS] Sugestion for PostgreSQL Developer´s TEAM!
I have a sugestion for pgsql 8.2 or next versions ... Is complicated encrypt the procedures/functions on Database like Oracle or similar? I sugest this because we develop ERP/MRP with complex routines and we like hide all of this routines...this is our "business secret". I know if we write this code in C, for exampleis possible to hide. But, we prefer pl/pgsql native. Thank´s, Marcio Delphi7+postgresql 8.x ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] PostgreSQL 8.0 - very good
Was the install very good, however am I needing to do something similar in the subject of the install to create users and services in Windows 2000/xp for an application, will it be that you could order me the script or project that you set up for this version 8.0 beta? Question: Does the version 8.0 already have programmed date to be thrown? Thank you
[BUGS]
unsubscribe pgsql-bugs ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] Possible problem with type bigserial in pg_dump/pg_restore
It seems to have a problem when making backup and restore with type
bigserial. I perceived when was restoring a database and the sequence
created for field bigserial was not correctly restored.
For example, i've created the follow structure:
CREATE TABLE cager.princ
(
cd_princ bigserial NOT NULL,
nm_princ character varying(50),
CONSTRAINT "pk-princ-cd_princ" PRIMARY KEY (cd_princ)
)
WITHOUT OIDS;
Making backup with:
C:\Arquivos de programas\pgAdmin III\1.6\pg_dump.exe -i -h 192.168.7.1 -p
5432 -U postgres -F c -b -v -f "C:\Temp\testepad.backup" testepad
Making restore with:
C:\Arquivos de programas\pgAdmin III\1.6\pg_restore.exe -i -h 192.168.7.1 -p
5432 -U postgres -d test1 -v "C:\Temp\testepad.backup"
The same table now is:
CREATE TABLE cager.princ
(
cd_princ bigint NOT NULL DEFAULT nextval('princ_cd_princ_seq'::regclass),
nm_princ character varying(50),
CONSTRAINT "pk-princ-cd_princ" PRIMARY KEY (cd_princ)
)
WITHOUT OIDS;
Take a look at the field cd_princ. Next value should be
'cager.princ_cd_princ_seq'.
I've tested it with pg_admin version 1.6.2 and 1.4.3.
If need more information, please, contact me.
Follow in annex messages on restoring.
Att.
Márcio A. Sepp
ZYON TECNOLOGIA LTDA
55 (49) 3444-4591
55 (49) 8405-9215
C:\Arquivos de programas\pgAdmin III\1.6\pg_restore.exe -i -h 192.168.7.1 -p
5432 -U postgres -d test1 -v "C:\Temp\testepad.backup"
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] Error while INITIALIZING:
pg_restore: [archiver (db)] could not execute query: ERROR: parameter
"standard_conforming_strings" cannot be changed
Command was: SET standard_conforming_strings = off;
pg_restore: creating SCHEMA cager
pg_restore: creating SCHEMA public
pg_restore: creating COMMENT SCHEMA public
pg_restore: creating TABLE princ
pg_restore: creating SEQUENCE princ_cd_princ_seq
pg_restore: creating SEQUENCE OWNED BY princ_cd_princ_seq
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 1514; 0 0 SEQUENCE OWNED BY
princ_cd_princ_seq postgres
pg_restore: [archiver (db)] could not execute query: ERROR: syntax error at or
near "OWNED"
LINE 1: ALTER SEQUENCE princ_cd_princ_seq OWNED BY princ.cd_princ;
^
Command was: ALTER SEQUENCE princ_cd_princ_seq OWNED BY princ.cd_princ;
pg_restore: executing SEQUENCE SET princ_cd_princ_seq
pg_restore: creating DEFAULT cd_princ
pg_restore: restoring data for table "princ"
pg_restore: creating CONSTRAINT pk-princ-cd_princ
pg_restore: setting owner and privileges for SCHEMA cager
pg_restore: setting owner and privileges for SCHEMA public
pg_restore: setting owner and privileges for COMMENT SCHEMA public
pg_restore: setting owner and privileges for ACL public
pg_restore: setting owner and privileges for TABLE princ
pg_restore: setting owner and privileges for SEQUENCE princ_cd_princ_seq
pg_restore: setting owner and privileges for SEQUENCE OWNED BY
princ_cd_princ_seq
pg_restore: setting owner and privileges for DEFAULT cd_princ
pg_restore: setting owner and privileges for CONSTRAINT pk-princ-cd_princ
WARNING: errors ignored on restore: 2
Process returned exit code 1.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
[BUGS] ENC: Possible problem with type bigserial in pg_dump/pg_restore
Pardon, in this example case it works ok. The problem is when i restore this
structure (this is my real case):
CREATE TABLE fat_m.ped_venda_it
(
cd_ped_venda_it_record bigserial NOT NULL,
...
...
)
When the table is created, the sequence is created too:
CREATE SEQUENCE fat_m.ped_venda_it_cd_ped_venda_it_record_seq
When i restore it, and try to insert a record the system show me the
message:
relation "ped_venda_it_cd_ped_venda_it_record" does not exist.
Maybe the problem occurred because the name is too long.
All the other sequence were restored fine.
Please, give me feedback about this problem. If i can help, i'll be
satisfied.
Att.
Márcio A. Sepp
ZYON TECNOLOGIA LTDA
(49) 3444-4591
(49) 8405-9215
> ______
> De: Marcio A. Sepp [mailto:[EMAIL PROTECTED]
> Enviada em: quarta-feira, 7 de fevereiro de 2007 12:51
> Para: 'pgsql-bugs@postgresql.org'
> Assunto: Possible problem with type bigserial in pg_dump/pg_restore
>
>
> It seems to have a problem when making backup and restore with type
> bigserial. I perceived when was restoring a database and the sequence
> created for field bigserial was not correctly restored.
>
> For example, i've created the follow structure:
>
> CREATE TABLE cager.princ
> (
> cd_princ bigserial NOT NULL,
> nm_princ character varying(50),
> CONSTRAINT "pk-princ-cd_princ" PRIMARY KEY (cd_princ)
> )
> WITHOUT OIDS;
>
> Making backup with:
> C:\Arquivos de programas\pgAdmin III\1.6\pg_dump.exe -i -h 192.168.7.1 -p
> 5432 -U postgres -F c -b -v -f "C:\Temp\testepad.backup" testepad
>
> Making restore with:
> C:\Arquivos de programas\pgAdmin III\1.6\pg_restore.exe -i -h 192.168.7.1
> -p 5432 -U postgres -d test1 -v "C:\Temp\testepad.backup"
>
> The same table now is:
>
> CREATE TABLE cager.princ
> (
> cd_princ bigint NOT NULL DEFAULT
> nextval('princ_cd_princ_seq'::regclass),
> nm_princ character varying(50),
> CONSTRAINT "pk-princ-cd_princ" PRIMARY KEY (cd_princ)
> )
> WITHOUT OIDS;
>
> Take a look at the field cd_princ. Next value should be
> 'cager.princ_cd_princ_seq'.
>
> I've tested it with pg_admin version 1.6.2 and 1.4.3.
>
> If need more information, please, contact me.
>
> Follow in annex messages on restoring.
>
>
>
>
> Att.
> Márcio A. Sepp
> ZYON TECNOLOGIA LTDA
> 55 (49) 3444-4591
> 55 (49) 8405-9215
>
C:\Arquivos de programas\pgAdmin III\1.6\pg_restore.exe -i -h 192.168.7.1 -p
5432 -U postgres -d test1 -v "C:\Temp\testepad.backup"
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] Error while INITIALIZING:
pg_restore: [archiver (db)] could not execute query: ERROR: parameter
"standard_conforming_strings" cannot be changed
Command was: SET standard_conforming_strings = off;
pg_restore: creating SCHEMA cager
pg_restore: creating SCHEMA public
pg_restore: creating COMMENT SCHEMA public
pg_restore: creating TABLE princ
pg_restore: creating SEQUENCE princ_cd_princ_seq
pg_restore: creating SEQUENCE OWNED BY princ_cd_princ_seq
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 1514; 0 0 SEQUENCE OWNED BY
princ_cd_princ_seq postgres
pg_restore: [archiver (db)] could not execute query: ERROR: syntax error at or
near "OWNED"
LINE 1: ALTER SEQUENCE princ_cd_princ_seq OWNED BY princ.cd_princ;
^
Command was: ALTER SEQUENCE princ_cd_princ_seq OWNED BY princ.cd_princ;
pg_restore: executing SEQUENCE SET princ_cd_princ_seq
pg_restore: creating DEFAULT cd_princ
pg_restore: restoring data for table "princ"
pg_restore: creating CONSTRAINT pk-princ-cd_princ
pg_restore: setting owner and privileges for SCHEMA cager
pg_restore: setting owner and privileges for SCHEMA public
pg_restore: setting owner and privileges for COMMENT SCHEMA public
pg_restore: setting owner and privileges for ACL public
pg_restore: setting owner and privileges for TABLE princ
pg_restore: setting owner and privileges for SEQUENCE princ_cd_princ_seq
pg_restore: setting owner and privileges for SEQUENCE OWNED BY
princ_cd_princ_seq
pg_restore: setting owner and privileges for DEFAULT cd_princ
pg_restore: setting owner and privileges for CONSTRAINT pk-princ-cd_princ
WARNING: errors ignored on restore: 2
Process returned exit code 1.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[BUGS] BUG #1658: Error download of odbc
The following bug has been logged online: Bug reference: 1658 Logged by: Marcio Roberto Chiaveli Email address: [EMAIL PROTECTED] PostgreSQL version: 7.2 Operating system: windows Description:Error download of odbc Details: When doing download of the driver ODBC, when I try descompacta-lo (unzip) him me of the the following mistake message: Cannot open file: it donates not uppear to be the valid archive. If you downloaded this file try downloading the file again. What cannot this happening? ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
