Oh bugger, I just discoved somthing that may throw a kink in things, here is one that has both a S and an L, but in this case since it has an L record in it we want to keep it :-(
I have a file that I need to parse multiple sections from the file.
The file contains multiple lines that start with ST (Abunch of data)
Then the file contains multiple lines that start with SE (Abunch of data)
SE*30*0001 ... (1 Reply)
I have a file that I need to parse multiple sections from the file.
The file contains multiple lines that start with ST (Abunch of data)
Then the file contains multiple lines that start with SE (Abunch of data)
SE*30*0001
ST*810*0002
I need all of the lines between and including these.... (6 Replies)
Here is a data file, which I believe is in YAML. I am trying to retrieve just the 'addon_domains" section, which doesnt seem to be as easy as I had originally thought. Any help on this would be greatly appreciated!! I have been trying to do this in awk and mostly bash scripting instead of perl... (3 Replies)
I've been trying to remove some lines of a xml file that looks like this:
<parent>
<child>name1</child>
<lots_of_other tags></lots_of_other_tags>
</parent>
<parent>
<child>name2</child>
<lots_of_other tags></lots_of_other_tags>
</parent>
<parent>
<child>name3</child>
... (5 Replies)
Hi All,
I have a file with the data 10;20;30;40;50;60;70;80;123;145;156;345. the output i want is the first fourth sixth elements and everything from there on. How do i achieve this. (1 Reply)
I have a file that looks liek this (see below). can somebody provide me with and awk or sed command that can take a piece of the file starting from the time to the blank line and put in into another file.
For example: How would I get the data from 10:56:11 to the blank line.
Two things:
... (5 Replies)
I have a configuration file that contains hundreds of these chunks. Each "chunk" is the section that begins with "define service {" and ends with "}".
define service {
check_command check_proc!java
hostgroup_name
service_description ... (5 Replies)
Hello,
I need some help with renaming some files by removing a certain portion of the filename.
The current file name is: ABC_2013186197_20130708_203556.95336
I need to remove the 5 digits after the first "_". The new file name should be:
ABC_197_20130708_203556.95336
I'm not quite... (5 Replies)
Hi,
I have a file with many sections in it. Each section is separated by a blank line.
The first line of each section would determine if the section is duplicate or not.
if the section is duplicate then remove the entire section from the file.
below is the example of input and output.... (5 Replies)
Hello experts,
I have a text file with lot of curly brackets (both opening { & closing } ). I need to delete them alongwith the text between opening & closing brackets' pair.
For ex: Input:-
59. Rh1 Qe4 {(Qf5-e4 Qd8-g8+ Kg6-f5
Qg8-h7+ Kf5-e5 Qh7-e7+ Ke5-f5 Qe7-d7+ Qe4-e6 Qd7-h7+ Qe6-g6... (6 Replies)
Discussion started by: prvnrk
6 Replies
LEARN ABOUT SUSE
prepare_transaction
PREPARE TRANSACTION(7) SQL Commands PREPARE TRANSACTION(7)NAME
PREPARE TRANSACTION - prepare the current transaction for two-phase commit
SYNOPSIS
PREPARE TRANSACTION transaction_id
DESCRIPTION
PREPARE TRANSACTION prepares the current transaction for two-phase commit. After this command, the transaction is no longer associated with
the current session; instead, its state is fully stored on disk, and there is a very high probability that it can be committed success-
fully, even if a database crash occurs before the commit is requested.
Once prepared, a transaction can later be committed or rolled back with COMMIT PREPARED [commit_prepared(7)] or ROLLBACK PREPARED [roll-
back_prepared(7)], respectively. Those commands can be issued from any session, not only the one that executed the original transaction.
From the point of view of the issuing session, PREPARE TRANSACTION is not unlike a ROLLBACK command: after executing it, there is no active
current transaction, and the effects of the prepared transaction are no longer visible. (The effects will become visible again if the
transaction is committed.)
If the PREPARE TRANSACTION command fails for any reason, it becomes a ROLLBACK: the current transaction is canceled.
PARAMETERS
transaction_id
An arbitrary identifier that later identifies this transaction for COMMIT PREPARED or ROLLBACK PREPARED. The identifier must be
written as a string literal, and must be less than 200 bytes long. It must not be the same as the identifier used for any currently
prepared transaction.
NOTES
This command must be used inside a transaction block. Use BEGIN [begin(7)] to start one.
It is not currently allowed to PREPARE a transaction that has executed any operations involving temporary tables, created any cursors WITH
HOLD, or executed LISTEN or UNLISTEN. Those features are too tightly tied to the current session to be useful in a transaction to be pre-
pared.
If the transaction modified any run-time parameters with SET (without the LOCAL option), those effects persist after PREPARE TRANSACTION,
and will not be affected by any later COMMIT PREPARED or ROLLBACK PREPARED. Thus, in this one respect PREPARE TRANSACTION acts more like
COMMIT than ROLLBACK.
All currently available prepared transactions are listed in the pg_prepared_xacts system view.
Caution:
It is unwise to leave transactions in the prepared state for a long time. This will interfere with the ability of VACUUM to reclaim
storage, and in extreme cases could cause the database to shut down to prevent transaction ID wraparound (see in the documentation).
Keep in mind also that the transaction continues to hold whatever locks it held. The intended usage of the feature is that a pre-
pared transaction will normally be committed or rolled back as soon as an external transaction manager has verified that other data-
bases are also prepared to commit.
If you have not set up an external transaction manager to track prepared transactions and ensure they get closed out promptly, it is
best to keep the prepared-transaction feature disabled by setting max_prepared_transactions to zero. This will prevent accidental
creation of prepared transactions that might then be forgotten and eventually cause problems.
EXAMPLES
Prepare the current transaction for two-phase commit, using foobar as the transaction identifier:
PREPARE TRANSACTION 'foobar';
SEE ALSO
COMMIT PREPARED [commit_prepared(7)], ROLLBACK PREPARED [rollback_prepared(7)]
SQL - Language Statements 2010-05-14 PREPARE TRANSACTION(7)