--- Luis Felipe Acevedo Fernandez
<[EMAIL PROTECTED]> wrote:
> Hi!
> I triyed to migrate a database from SqlServer to
> PostgreSql, but I have a
> problem with char or varchar data types cos If I try
> to insert or select some
> information from a table the program retrieve blank
> spaces, my p
--- Geoff <[EMAIL PROTECTED]> wrote:
> Sorry if this is a question that has been answered
> in some form or another,
> but I need to know if there is a toold of some
> description that will help me
> get a diagram of my 7.2.1 database with the
> relationships.
-- There is a tool call ERWin (by
--- Roger Mathis <[EMAIL PROTECTED]> wrote:
> Hi
>
> Is there a possibility to shut down the
> Auto-Commit-Funktion?
> Thanks
Use "BEGIN WORK" or "BEGIN TRANSACTION" statement
before typing other SQL statements. This will ensure
that the database will only commit if you type
"COMMIT"
ludwig.
--- Benny <[EMAIL PROTECTED]> wrote:
> I can't access postegresl via ODBC, because 5432
> port seems to be closed.
> How can I open it?
--> Try checking your firewall settings (IPChains /
IPTables) and see if its blocking port 5432.
Hope that helps,
ludwig.
_
Hi:
--- Michiel Lange <[EMAIL PROTECTED]> wrote:
> seems like:
> there's read/write, write, write access on the file.
> I think the others might want to be able to read the
> file instead of writing
> to it.
>
> "Andrey Romanchenko" <[EMAIL PROTECTED]>
> schreef in bericht
> news:a4t5vu$1jt2$1@;j
Hi:
Is there a way of logging the RAISE statements in a
plpgsql function to a logfile (aside from syslog)? I
noticed that all RAISE statments are only logged in
the syslog.
The following is a portion my current configuration
related to logging:
log_connection = true
log_timestamp = tr
Hi shreedhar :
--- shreedhar <[EMAIL PROTECTED]> wrote:
> Can any body tell that how sub queries and joins
> differs funcationally.
> Because sub queries taking lot of time than joins.
>
The following could be the probable reasons:
a) Your are using correlated queries - Correlated
queries al
Do I need to upgrade Postgresql? By the way there
are some errors if backup a 7.2 db and restore in 7.3
db. In 7.2 you can do something like "SELECT
CURRENT_TIMESTAMP()" in a plpgsql function, while this
will cause in an error in 7.3.
Do I need to ch
Hi:
I notice the following error message in my
postgresql log file:
FATAL : s_lock (0x401db020) at lwlock.c Stuck
spinlock. Aborting
Version of my postgresql :
PostgreSQL 7.2.3 on i686-pc-linux-gnu compiled by GCC
2.96
Operating System : RedHat 7.1
Thanks in advance,
ludwig lim
