First a moderative hint: you should open a separate thread for different problems, as this will it make easier to search for a specific problem for the future user with a similar (or even the same) problem. Thanks for your consideration.
From what you describe your terminal type is definitely at fault. Either your putty is not configured to act like a vt100 terminal (don't know putty all too well, being blessed with a Unix system to work on) or your termcap database entries for the vt100 are crap. As you said the system is a freshly installed AIX system i suppose the former to be the case.
To make sure the usual terminal definitions are correctly installed issue the following command. Output should be more or less the same as mine (taken from an AIX 5.3 system at ML 09):
Hi,
I m new to Solaris CDE...earlier i was using Windows.
Here is my problem..
i know that whatever the initial settings we need to execute,we can place them in .profile file.
in my home dir (/home/venki),i have following files for that.
.profile
.profile.user
.kshrc
.kshrc.user
... (2 Replies)
An odd problem using .kshrc, if I run with this in my home login directory it works fine other than if I use 'man', where each word of the manual entry is on a seperate line ?. I'm using AIX 5.3 (it worked fine on 5.2). Anyone seen this before ? (3 Replies)
Can anyone tell me why .profile would not be reading my .kshrc file?
O/S is SCO 5.06? I've placed echo's before & after setting ENV and
nothing ... help?
Thanks!
Here's .profile
==================================================
:
# DoubleVision Pro's digiboard call during... (7 Replies)
Hi,
My login shell is c shell
I have a line in .cshrc like
setenv a 1000
I have a line in .profile like
ENV=$HOME/.kshrc
export ENV
and in my .kshrc
a=10
export a
I wrote one korn script
#!/bin/ksh
echo $a (3 Replies)
Hi All.
I created a cronjob entry and for some reason it is not executing. The script that it is suppose to call sends me an email when it is done. When I run the job manually it executes fine. This how my cron entry looks:
00 14 * * * /home/oracle/scripts/bin/free_space/free_space.sh 2>$1... (5 Replies)
Hi friends
NO errors, but when I try to execute the program it gets struck.
Can any one find it out.
#include<stdio.h>
#include<sys/types.h>
#include<sys/mman.h>
#include<stdlib.h>
#include<fcntl.h>
#include<sys/stat.h>
#include<unistd.h>
#include<signal.h>
#include<string.h>
... (0 Replies)
Hi friends
When I compile thic program by gcc filename, it shows no error.
But after that if I execute the program gets stuck.
Can any one find out.
#include<stdio.h>
#include<sys/types.h>
#include<sys/mman.h>
#include<stdlib.h>
#include<fcntl.h>
#include<sys/stat.h>... (6 Replies)
Hi,
am facing some problem while inserting a record into a script
Please find script below.
`sqlplus -s asdf/asdf123 <<eof!
set feedback off;
set heading off;
set verify off;
insert into... (3 Replies)
I have this script
#!/bin/ksh
#set -x
if
then
while
do
if
then
date >> /export/home/Tool/checktmp.log
echo "`ls -lrt / | grep tmp`" >> /export/home/Tool/checktmp.log
echo "`ls -lrt / | grep tmp`" | mailx -s "/tmp permission has changed" -r a.com b.com c.com d.com
... (2 Replies)
So Yesterday I switched from Solus Linux to Fedora Linux 30, but I forgot to backup some of my dotfiles including kshrc. I am fairly new to Korn shell and do not know it well, but through memory I was able to at least get this. I did use code from several different source to recreate it. The only... (13 Replies)
Discussion started by: zoomer
13 Replies
LEARN ABOUT NETBSD
set_transaction
SET TRANSACTION(7) SQL Commands SET TRANSACTION(7)NAME
SET TRANSACTION - set the characteristics of the current transaction
SYNOPSIS
SET TRANSACTION transaction_mode [, ...]
SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
where transaction_mode is one of:
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
READ WRITE | READ ONLY
DESCRIPTION
The SET TRANSACTION command sets the characteristics of the current transaction. It has no effect on any subsequent transactions. SET SES-
SION CHARACTERISTICS sets the default transaction characteristics for subsequent transactions of a session. These defaults can be overrid-
den by SET TRANSACTION for an individual transaction.
The available transaction characteristics are the transaction isolation level and the transaction access mode (read/write or read-only).
The isolation level of a transaction determines what data the transaction can see when other transactions are running concurrently:
READ COMMITTED
A statement can only see rows committed before it began. This is the default.
SERIALIZABLE
All statements of the current transaction can only see rows committed before the first query or data-modification statement was exe-
cuted in this transaction.
The SQL standard defines two additional levels, READ UNCOMMITTED and REPEATABLE READ. In PostgreSQL READ UNCOMMITTED is treated as READ
COMMITTED, while REPEATABLE READ is treated as SERIALIZABLE.
The transaction isolation level cannot be changed after the first query or data-modification statement (SELECT, INSERT, DELETE, UPDATE,
FETCH, or COPY) of a transaction has been executed. See in the documentation for more information about transaction isolation and concur-
rency control.
The transaction access mode determines whether the transaction is read/write or read-only. Read/write is the default. When a transaction is
read-only, the following SQL commands are disallowed: INSERT, UPDATE, DELETE, and COPY FROM if the table they would write to is not a tem-
porary table; all CREATE, ALTER, and DROP commands; COMMENT, GRANT, REVOKE, TRUNCATE; and EXPLAIN ANALYZE and EXECUTE if the command they
would execute is among those listed. This is a high-level notion of read-only that does not prevent all writes to disk.
NOTES
If SET TRANSACTION is executed without a prior START TRANSACTION or BEGIN, it will appear to have no effect, since the transaction will
immediately end.
It is possible to dispense with SET TRANSACTION by instead specifying the desired transaction_modes in BEGIN or START TRANSACTION.
The session default transaction modes can also be set by setting the configuration parameters default_transaction_isolation and
default_transaction_read_only. (In fact SET SESSION CHARACTERISTICS is just a verbose equivalent for setting these variables with SET.)
This means the defaults can be set in the configuration file, via ALTER DATABASE, etc. Consult in the documentation for more information.
COMPATIBILITY
Both commands are defined in the SQL standard. SERIALIZABLE is the default transaction isolation level in the standard. In PostgreSQL the
default is ordinarily READ COMMITTED, but you can change it as mentioned above. Because of lack of predicate locking, the SERIALIZABLE
level is not truly serializable. See in the documentation for details.
In the SQL standard, there is one other transaction characteristic that can be set with these commands: the size of the diagnostics area.
This concept is specific to embedded SQL, and therefore is not implemented in the PostgreSQL server.
The SQL standard requires commas between successive transaction_modes, but for historical reasons PostgreSQL allows the commas to be omit-
ted.
SQL - Language Statements 2010-05-14 SET TRANSACTION(7)