Bonjour,

Je souhaiterai connaître les impacts du redimensionnement des paramètres -with-segsize=64 --with-wal-segsize=64 --with-blocksize=16 --with-wal-blocksize=16, à la fois d'une manière générale et pour les petites bases de données.

Bonjour,

A l'utilisation d'ora2Pg, nous obtenons le message suivant:

DBD::Pg::db do failed: ERROR:  relation "depotvalide" does not exist
FATAL: ERROR:  relation "depotvalide" does not exist

Pouvez vous nous aider à détecter le pb ?

La trace en amont à ce message est:

****************************************
Traces produites par ora2pg
****************************************

Trying to connect to database: dbi:Oracle:host=devfntd0.xxx.xxx.xxx;port=1521;sid=MAS
Isolation level: SET TRANSACTION ISOLATION LEVEL READ COMMITTED
Force Oracle to compile schema before code extraction
Retrieving table information...
[1] Scanning ADRESSECORRESPONDANCE ( ESSAIADRESSECORRESPONDANCE TABLE )...
     ...
[2] Scanning CACHETOPOCOM ( ESSAICACHETOPOCOM TABLE )...
       
[4] Scanning CAMPAGNEENCOURS ( ESSAICAMPAGNEENCOURS TABLE )...
       
[5] Scanning CONTEXTEUTILISATEUR ( ESSAICONTEXTEUTILISATEUR TABLE )...
       
[6] Scanning CORRESPCOMTOPAD ( ESSAICORRESPCOMTOPAD TABLE )...
       
[7] Scanning DEFAILLANCE ( ESSAIDEFAILLANCE TABLE )...
       
[8] Scanning DEPOTARECYCLER ( ESSAIDEPOTARECYCLER TABLE )...
       
[9] Scanning DEPOTVALIDE ( ESSAIDEPOTVALIDE TABLE )...
       
[10] Scanning ENUMERATION ( ESSAIENUMERATION TABLE )...
       
[11] Scanning STATISTIQUES ( ESSAISTATISTIQUES TABLE )...
       
[12] Scanning SUPPORTJURIDIQUE ( ESSAISUPPORTJURIDIQUE TABLE )...
       
[13] Scanning TELEPHONESTRT ( ESSAITELEPHONESTRT TABLE )...
       
[14] Scanning TIERS ( ESSAITIERS TABLE )...
       
[15] Scanning TIERSAMBRESUPPRIMES ( ESSAITIERSAMBRESUPPRIMES TABLE )...
       
[16] Scanning TYPEDECLARATION ( ESSAITYPEDECLARATION TABLE )...
       
Retrieving table information...
[1] Scanning ADRESSECORRESPONDANCE ( ESSAIADRESSECORRESPONDANCE TABLE )...
Warning duplicate table ADRESSECORRESPONDANCE, SYNONYME ? Skipped.
[1] Scanning CACHETOPOCOM ( ESSAICACHETOPOCOM TABLE )...
Warning duplicate table CACHETOPOCOM, SYNONYME ? Skipped.
[1] Scanning CACHETOPODEP ( ESSAICACHETOPODEP TABLE )...
Warning duplicate table CACHETOPODEP, SYNONYME ? Skipped.
[1] Scanning CAMPAGNEENCOURS ( ESSAICAMPAGNEENCOURS TABLE )...
Warning duplicate table CAMPAGNEENCOURS, SYNONYME ? Skipped.
[1] Scanning CONTEXTEUTILISATEUR ( ESSAICONTEXTEUTILISATEUR TABLE )...
Warning duplicate table CONTEXTEUTILISATEUR, SYNONYME ? Skipped.
[1] Scanning CORRESPCOMTOPAD ( ESSAICORRESPCOMTOPAD TABLE )...
Warning duplicate table CORRESPCOMTOPAD, SYNONYME ? Skipped.
[1] Scanning DEFAILLANCE ( ESSAIDEFAILLANCE TABLE )...
Warning duplicate table DEFAILLANCE, SYNONYME ? Skipped.
[1] Scanning DEPOTARECYCLER ( ESSAIDEPOTARECYCLER TABLE )...
Warning duplicate table DEPOTARECYCLER, SYNONYME ? Skipped.
[1] Scanning DEPOTVALIDE ( ESSAIDEPOTVALIDE TABLE )...
Warning duplicate table DEPOTVALIDE, SYNONYME ? Skipped.
[1] Scanning ENUMERATION ( ESSAIENUMERATION TABLE )...
Warning duplicate table ENUMERATION, SYNONYME ? Skipped.
[1] Scanning STATISTIQUES ( ESSAISTATISTIQUES TABLE )...
Warning duplicate table STATISTIQUES, SYNONYME ? Skipped.
[1] Scanning SUPPORTJURIDIQUE ( ESSAISUPPORTJURIDIQUE TABLE )...
Warning duplicate table SUPPORTJURIDIQUE, SYNONYME ? Skipped.
[1] Scanning TELEPHONESTRT ( ESSAITELEPHONESTRT TABLE )...
Warning duplicate table TELEPHONESTRT, SYNONYME ? Skipped.
[1] Scanning TIERS ( ESSAITIERS TABLE )...
Warning duplicate table TIERS, SYNONYME ? Skipped.
[1] Scanning TIERSAMBRESUPPRIMES ( ESSAITIERSAMBRESUPPRIMES TABLE )...
Warning duplicate table TIERSAMBRESUPPRIMES, SYNONYME ? Skipped.
[1] Scanning TYPEDECLARATION ( ESSAITYPEDECLARATION TABLE )...
Warning duplicate table TYPEDECLARATION, SYNONYME ? Skipped.
Dumping table TELEPHONESTRT...
Dumping table TIERSAMBRESUPPRIMES...
Dumping table CONTEXTEUTILISATEUR...
Dumping table DEPOTVALIDE...

La commande ora2Pg est:

ora2pg -c monFichier.conf -d

le fichier monFichier.conf:

####################  Ora2Pg Configuration file   #####################

# Support for including common config file that may containt any
# of the following configuration directives.
#IMPORT common.conf

# Set this directive to a file containing PL/SQL Oracle Code like function,
# procedure or a full package body to prevent Ora2Pg from connecting to an
# Oracle database end just apply his convertion tool to the content of the
# file. This can only be used with the following export type: PROCEDURE,
# FUNCTION or PACKAGE. If you don't know what you do don't use this directive.
#INPUT_FILE     ora_plsql_src.sql

# Set the Oracle home directory
ORACLE_HOME     /oracle/11g

# Set Oracle database connection (datasource, user, password)
# Your SID should be declared on your tnsnames.ora file
ORACLE_DSN      dbi:Oracle:host=devfntd0.xxx.xxx.xxx;port=1521;sid=MAS
ORACLE_USER     system
ORACLE_PWD      xxx

# Set this to 1 if you connect as simple user and can not extract things
# from the DBA_... tables. It will use tables ALL_... This will not works
# with GRANT export, you should use an Oracle DBA username at ORACLE_USER
USER_GRANTS     0

# Trace all to stderr
DEBUG           0

# Export Oracle schema to PostgreSQL schema
EXPORT_SCHEMA   1

# Oracle schema/owner to use
SCHEMA          FNTD

# Enable this directive to force Oracle to compile schema before exporting code.
# This will ask to Oracle to validate the PL/SQL that could have been invalidate
# after a export/import for example. If you set the value to 1 will exec:
# DBMS_UTILITY.compile_schema(schema => sys_context('USERENV', 'SESSION_USER'));
# but if you probvide the name of a particular schema it will use the following
# command: DBMS_UTILITY.compile_schema(schema => 'schamename');
COMPILE_SCHEMA  0

# PostreSQL search path schem to use. Can be a coma delimited list,
# for example: users_schem,public will result in the following PostgreSQL
# schema path: SET search_path = users_schema,public;
# By default search_path is set to Oracle schema and pg_catalog.
PG_SCHEMA       FNTD

# Type of export. Values can be the following keyword:
#       TABLE           Export tables
#       PACKAGE         Export packages
#       DATA            Export datas from table as INSERT statement
#       COPY            Export datas from table as COPY statement
#       VIEW            Export views
#       GRANT           Export grants
#       SEQUENCE        Export sequences
#       TRIGGER         Export triggers
#       FUNCTION        Export functions
#       PROCEDURE       Export procedures
#       TABLESPACE      Export tablespace (PostgreSQL >= 8 only)
#       TYPE            Export user defined Oracle types
#       PARTITION       Export range or list partition (PostgreSQL >= v8.4)
#TYPE           TABLE,GRANT,TABLESPACE,COPY
TYPE            TABLE,COPY

# Set which table to export from. By default export from all tables.
# Additionally the extraction will respect the table list order given
# here. This is usefull if you have lots of foreign key constraints.
# Value must be a list of table name separated by space.
#TABLES         TABLE_TEST

# Set which table to exclude from extraction process. By default none.
# Value must be a list of table name separated by space.
#EXCLUDE                OTHER_TABLES

# Support for turning off certain schema features in the postgres side
# during schema export. Values can be : fkeys, pkeys, ukeys, indexes, checks
# separated by a space character.
# fkeys         : turn off foreign key constraints
# pkeys         : turn off primary keys
# ukeys         : turn off unique column constraints
# indexes       : turn off all other index types
# checks        : turn off check constraints
SKIP    fkeys pkeys ukeys indexes checks

# Extract data by bulk of DATA_LIMIT tuples at once. Default 10000. If you set
# a high value be sure to have enougth memory if you have million of rows.
DATA_LIMIT      10000

# You may wish to just extract data from some fields, the following directives
# will help you to do that. Works only with TYPE = DATA or COPY
# Modify output from the following tables(fields separate by space or comma)
#MODIFY_STRUCT  TABLE_TEST(dico,dossier)

# You may wish to change table names during data extraction, especally for replication use.
# Give a liste of tables separate by space as follow. Works only with TYPE = DATA or COPY
# REPLACE_TABLES        ORIG_TABLE_NAME1:NEW_TABLE_NAME1 ORIG_TABLE_NAME2:NEW_TABLE_NAME2

# You may wish to change column names during data extraction, especally for replication use.
# Give a liste of tables and columns separate by space as follow. Works only with TYPE = DATA or COPY
# REPLACE_COLS  ORIG_TABLE_NAME(ORIG_COL_NAME1:NEW_COL_NAME1,ORIG_COL_NAME2:NEW_COL_NAME2)

# Define the following directive to send export directly to a PostgreSQL database
# This will disable file output.
#PG_DSN         dbi:Pg:dbname=mas;host=localhost;port=5433
#PG_DSN         dbi:Pg:dbname=mas;host=10.xxx.xxx.159;port=5433
PG_DSN          dbi:Pg:dbname=gr3;host=10.xxx.xxx.214;port=5438
PG_USER postgres
PG_PWD          xxx

# By default all object names are converted to lower case, if you
# want to preserve Oracle object name asis set this to 1. Not recommanded
# unless you always quote all tables and columns on all your scripts.
CASE_SENSITIVE  0

# Support for include a WHERE clause filter when dumping the contents
# of tables. Value is construct as follow: TABLE_NAME[WHERE_CLAUSE], or
# if you have only one where clause for each table just put the where
# clause as value. Both are possible too. Here are some examples:
#WHERE  1=1     # Apply to all tables
#WHERE  TABLE_TEST[ID1='001']   # Apply only on table TABLE_TEST
#WHERE  TABLE_TEST[ID1='001' AND ID1='002] DATE_CREATE > '2001-01-01' TABLE_INFO[NAME='test']
# The last applies two different where clause on tables TABLE_TEST and TABLE_INFO and
# a generic where clause on DATE_CREATE to all other tables

# By default all output is dump to STDOUT if not send directly to postgresql
# database (see above). Give a filename to save export to it. If you want
# a Gzipped compressed file just add the extension .gz to the filename, you
# need perl module Compress::Zlib from CPAN. Add extension .bz2 to use Bzip2
# compression
#OUTPUT         output.sql.gz
#OUTPUT         output.sql.bz2
#OUTPUT         result.sql

# Base directory where all dumped files must be written
#OUTPUT_DIR     /var/tmp

# Path to the bzip2 program. See OUTPUT directive above.
BZIP2   /usr/bin/bzip2

# Set this to 1 to replace default password for all extracted user
# during GRANT export
GEN_USER_PWD    0

# When exporting tables, Ora2Pg normally exports constraints as they are;
# if they are non-deferrable they are exported as non-deferrable.
# However, non-deferrable constraints will probably cause problems when
# attempting to import data to PostgreSQL. The following option set to 1
# will cause all foreign key constraints to be exported as deferrable
FKEY_DEFERRABLE 0

# In addition when exporting data the DEFER_FKEY option set to 1 will add
# a command to defer all foreign key constraints during data export and
# the import will be done in a single transaction. This will work only if
# foreign keys have been exported as deferrables. Constraints will then be
# checked at the end of the transaction.
DEFER_FKEY      1

# If deferring foreign keys is not possible du to the amount of data in a
# single transaction or you've not exported foreign keys as deferrables
# you can use the DROP_FKEY directive. It will drop all foreign keys before
# data import and recreate them at the end.
DROP_FKEY       1

# Enabling this directive force Ora2Pg to drop all indexes on data import
# tables, except automatic index on primary key, and recreate them at end
# of data import. This may improve speed a lot during a fresh import.
DROP_INDEXES    1

# If set to 1 replace portable numeric type into PostgreSQL internal type.
# Oracle data type NUMBER(p,s) is approximatively converted to smallint,
# integer, bigint, real and float PostgreSQL data type. If you have monetary
# fields you should preserve the numeric(p,s) PostgreSQL data type if you need
# very good precision. NUMBER without precision are set to float.
PG_NUMERIC_TYPE 1

# NUMBER(x) are converted by default to bigint if PG_NUMERIC_TYPE is true.
# You can overwrite this value to any PG type, like integer or bigint.
DEFAULT_NUMERIC bigint

# By default, primary key names in the source database are ignored, and
# default key names are created in the target database. If this is set to true,
# primary key names are kept.
KEEP_PKEY_NAMES 1

# Disables triggers on all tables in COPY or DATA mode. Available modes
# are USER (userdefined triggers) and ALL (includes RI system
# triggers). Set to 0 if you don't want to disable triggers during
# data migration.
DISABLE_TABLE_TRIGGERS 1

# By default all datas that are not of type character, date or time are
# escaped. If you experience any problem with that you can set it to 1
# to disable it.
NOESCAPE        0

# If you're experiencing problems in data type export, the following directive
# will help you to redefine data type translation used in Ora2pg. The syntax is
# a coma separated list of "Oracle datatype:Postgresql datatype". Here are the
# data type that can be redefined and their default value.
# DATA_TYPE     DATE:timestamp,LONG:text,LONG RAW:text,CLOB:text,NCLOB:text,BLOB:bytea,BFILE:text,RAW:bytea,ROWID:oid,FLOAT:double precision,DEC:decimal,DECIMAL:decimal,DOUBLE PRECISION:double precision,INT:integer,INTEGER:integer,REAL:real,SMALLINT:smallint,BINARY_FLOAT:double precision,BINARY_DOUBLE:double precision,TIMESTAMP:timestamp,XMLTYPE:xml,BINARY_INTEGER:integer,PLS_INTEGER:integer

# Enforce default language setting following the Oracle database encoding. This
# may be used with mutibyte characters like UTF8.
# This will set  to the given value.
#NLS_LANG       AMERICAN_AMERICA.UTF8
NLS_LANG        french_france.WE8ISO8859P1

# Enforce perl to use binary mode for output using the given encoding. This
# must be used if you experience the perl message: "Wide character in print"
# The warning happens when you output a Unicode string to a non-unicode
# filehandle. If you set it to 'utf8' as follow, it will force printing
# like this: binmode OUTFH, ":utf8";
#BINMODE                utf8

# Allow to add a coma separated list of system user to exclude from
# from Oracle extraction. Oracle have many of them following the modules
# installed. By default it will suppress all object owned by the following
# system users:
#       SYS,SYSTEM,DBSNMP,OUTLN,PERFSTAT,CTXSYS,XDB,WMSYS,SYSMAN,SQLTXPLAIN,
#       MDSYS,EXFSYS,ORDSYS,DMSYS,OLAPSYS,FLOWS_020100,FLOWS_FILES,TSMSYS
# Other list of users set to this directive will be added to this list.
#SYSUSERS

# Disables alter of sequences on all tables in COPY or DATA mode.
# Set to 1 if you want to disable update of sequence during data migration.
DISABLE_SEQUENCE        0

# Force to use Oracle case sensitive table/view name. Default disabled.
ORA_SENSITIVE   0

# Enable PLSQL to PLPSQL convertion. This is a work in progress, feel
# free modify/add you own code and send me patches. The code is under
# function plsql_toplpgsql in Ora2PG/PLSQL.pm. Default disabled.
PLSQL_PGSQL     1

# Allow escaping of column name using Oracle reserved words.
ORA_RESERVED_WORDS      audit,comment

# Allow object constraints to be saved in a separate file during schema export.
# The file will be named CONSTRAINTS_OUTPUT. Where OUTPUT is the value of the
# corresponding configuration directive. You can use .gz xor .bz2 extension to
# enable compression. Default is to save all data in the OUTPUT file. This
# directive is usable only with TABLE export type.
FILE_PER_CONSTRAINT     0

# Allow indexes to be saved in a separate file during schema export. The file
# will be named INDEXES_OUTPUT. Where OUTPUT is the value of the corresponding
# configuration directive. You can use .gz xor .bz2 file extension to enable
# compression. Default is to save all data in the OUTPUT file. This directive
# is usable only with TABLE export type.
FILE_PER_INDEX          0

# Allow data export to be saved in one file per table/view. The files
# will be named as tablename_OUTPUT. Where OUTPUT is the value of the
# corresponding configuration directive. You can use .gz xor .bz2
# extension to enable compression. Default is to save all data in one
# file. This is usable only during DATA or COPY export type.
FILE_PER_TABLE  0

# This directive may be used if you want to change the default isolation
# level of the data export transaction. Default is now to set the level
# to a serializable transaction to ensure data consistency. Here are the
# allowed value of this directive: readonly, readwrite, serializable and
# committed (read commited).
#TRANSACTION    serializable
TRANSACTION     committed

# Allow support of WHEN clause in trigger definition PG>=9.0
PG_SUPPORTS_WHEN                1

# Allow support of INSTEAD OF in triggers definition PG>=9.1
PG_SUPPORTS_INSTEADOF   0

# Allow function export to be saved in one file per function/procedure.
# The files will be named as funcname_OUTPUT. Where OUTPUT is the value
# of the corresponding configuration directive. You can use .gz xor .bz2
# extension to enable compression. Default is to save all data in one
# file. This is usable only during FUNCTION or PROCEDURE export type.
FILE_PER_FUNCTION       0

# Add a TRUNCATE TABLE instruction before loading data on COPY and DATA
# export.
TRUNCATE_TABLE  0

# If you experience ERROR: invalid byte sequence for encoding "UTF8": 0xe87472
# when loading data you may want to set the encoding of the PostgreSQL client.
# By default it is not set and it will depend of you system client encoding.
#CLIENT_ENCODING        LATIN1

# By default the owner of database objects is the one you're using to connect
# to PostgreSQL. If you use an other user (postgres for exemple) you can force
# Ora2Pg to set the object owner to be the one used in the Oracle database by
# setting the directive to 1, or to a completely different username by setting
# the directive value # to that username.
FORCE_OWNER     0

# This controls whether ordinary string literals ('...') treat backslashes
# literally, as specified in SQL standard. This was the default before Ora2Pg
# v8.5 so that all stringis was escaped first, now this is currently on, causing
# Ora2Pg will now use the escape string syntax (E'...') if this parameter is not
# set to off or 0. This is the exact behaviour of the same option in PostgreSQL
# This is used only during DATA export type to build INSERT statements.
STANDARD_CONFORMING_STRINGS     1

# Multi-threading support. It is only used to do the escaping to convert
# LOBs to byteas, as it is very cpu hungry.
# There's a lot of CPU-waste here. Putting 6 threads will only triple your
# throughput, if your machine has enough cores.
# If zero, do not use threads, do not waste CPU, but be slower with bytea.
# Performance seems to peak at 5 threads, if you have enough cores, and
# triples throughput on tables having LOB.
# Another important thing: because of the way threading works in perl, threads
# consume a lot of memory. Put a low (5000 for instance) DATA_LIMIT if you
# activate threading. Default is threads disabled.
THREAD_COUNT            0

_EDIT jpargudo__
=> Rendre anonyme le nom des bases, ips et logins..

Bonjour,

Je cherche des expériences dans l'utilisation d'outils graphiques permettant l'analyse proactive des bases de données PostgreSQL en vue d'optimiser les bases de données PostgreSQL.

S'il n'en existe pas ou peu performant. Que préconisez-vous comme lot d'outils qui répondraient à la demande ?

merci

hervé

Bonjour,

nous envisageons la possibilité d'héberger sur nos machines plusieurs versions de PostgreSQL.
A savoir la 8.3.9 et la 8.4.4 dans un premier temps sur du LINUX centos5.3

Nous utilisons les fichiers .spec fournis par la communauté car nous souhaiterions installer le moteur et toutes les dépendances liées à la plateforme et ceux non liées à la plateforme dans un répertoire de la forme:

/U01/pgsql/8.3.11/bin
/U01/pgsql/8.3.11/include
/U01/pgsql/8.3.11/lib
.....etc

Afin de réaliser cette opérations, nous nous sommes lancés dans la mise en oeuvre du fichier .spec fournit par la communauté en modifiant le moins de chose possible pour rester en conformité avec les normes.

Nous appelons la recompilation avec:

rpmbuild -ba postgresql-$VERSION.DGFIP.spec \
        --define "_prefix /u01/pgsql/$VERSION" \
        --define "_exec_prefix /usr" \
        --define "_includedir /usr/include" \
        --define "_bindir /u01/pgsql/$VERSION/bin" \
        --define "_datadir /u03" > log.txt

Et le résultat est:

./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/u01/pgsql/8.3.11 --exec-prefix=/usr --bindir=/u01/pgsql/8.3.11/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/u03 --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/u01/pgsql/8.3.11/com --mandir=/usr/share/man --infodir=/usr/share/info --disable-rpath --with-perl --with-python --with-tcl --with-tclconfig=/usr/lib --with-openssl --with-pam --with-krb5 --with-gssapi --with-includes=/usr/include --with-libraries=/usr/lib --enable-nls --enable-thread-safety --with-ossp-uuid --with-libxml --with-libxslt --with-ldap --with-system-tzdata=/u03/zoneinfo --sysconfdir=/etc/sysconfig/pgsql --datadir=/u03 --with-docdir=/usr/share/doc

Nous pensions qu'en variabilisant exec_prefix avec /u01/pgsql/$VERSION, cela fonctionnerait. Malheureusement le fichier .spec des versions 8.3.11 et 8.4.4 de la communauté souffre d'un manque de variabilisation. Par conséquent, nous sommes obligés de laisser certaines parties comme exec_prefix /usr, de spécifier includedir /usr/include pour que la recompilation fonctionne...

Quelle méthode suggérez vous(avec des exemples svp) pour recompiler avec fichier spec sans modifier les fichiers spec de la communauté afin que tout moteur postgresql s'installe dans /u01/pgsql/version ?

Merci pour votre aide.

hfilliere

Bonjour,

L'installation (modulo quelques details) s'est bien passée et la version 8.3.8 se lance bien sur notre serveur.
Par contre il reste le problème de PHP/apache. Celui-ci semble ne pas pouvoir se connecter DE TEMPS EN TEMPS.

Le code suivant :
<?php

ini_set('track_errors','on');

$conn = @pg_connect("host=localhost dbname=toto user=dico password=toto");

echo "Connection result: ";
print_r($conn);
echo "<hr>";

if ($conn===false) {
    echo "Connection failed: ";
        print_r($php_errormsg);
            echo "<hr>";
            }       
?>

renvoie en général cela
Connection result: Resource id #2

mais de temps en temps ceci :
Connection failed: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: could not connect to server: Is the server running on host "localhost" and accepting TCP/IP connections on port 5432

Avez-vous déjà eu des retours sur ce problème ?

Quels sont vos suggestions/idées ?

merci pour votre aide...je suis sec !

hfilliere

Bonjour à nouveau ,

De la même façon que dans mon précédent Post, je cherche à optimiser les écritures de journaux de transactions. Toujours dans Linux MAG je lis qu'il est intéressant de paramétrer un checkpoint_segments à 10 et un checkpoint_completion_target à 0.9..

Pour quel type d'application est-ce le plus recommandé ?(OLTP...etc)

Qu'en est il pour le checkpoint_timeout ? (5mn par défaut) ? est-ce une valeur acceptable ou faut il généralement l'augmenter ?

merci pour vos lumières.

Bonjour,

Bonnes années à tous !

je souhaiterai connaître quelle version de JDBC piochée sous http://jdbc.postgresql.org/ dois-je utiliser pour une postgresql v8.3.X. Quels sont vos recommandations ?

Merci d'avance.

Hfilliere

Bonjour,

Afin de monter en version un moteur PostgreSQL 8.3.[0-5] vers 8.3.8, j'ai lu et compris qu'il fallait simplement écraser les anciens binaires.

Est-ce que je suis dans le vrai ?

Sinon quels sont les points à surveiller ? Que faut-il faire ?
Quels sont les éventuels impacts pour les bases ?

merci de votre aide.

hfilliere