10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have c program that I run like this:
./a.out t1
And my test files look like this all the way up to 100:
t1
t2
t3
Is there a way to run this more efficiently so I don't have to hit up and change the number every time? (4 Replies)
Discussion started by: cokedude
4 Replies
2. Shell Programming and Scripting
1)In a particualr path i have a set of inputfiles like
path:/defaultmis/MonthlyLoads/INFA_EXPORT_022013/map*
example:
1)map_de
2)map_cod
3)map_feg
........and so on
in above path there wil be nearly 15 to 20 files starting with map and in other path i have another file input file... (4 Replies)
Discussion started by: katakamvivek
4 Replies
3. Shell Programming and Scripting
I can rename a file with sequential numbers from 1 to N with this script:
num=1
for file in *.dat;do
mv "$file" "$(printf "%u" $num).txt"
let num=num+1
done
The script begins with renaming a some.dat file to 1.dat.txt and goes on sequentially renaming other DAT files to... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies
4. Programming
Writing a Tool to simulate non-sequential disk I/O (simulate db file sequential read) in C POSIX
I have over the years come across the same issue a couple of times, and it normally is that the read speed on SAN is absolutely atrocious when doing non-sequential I/O to the disks. Problem being of... (7 Replies)
Discussion started by: vrghost
7 Replies
5. Shell Programming and Scripting
Hi
I have a file sequential way i.e. written in contineous mode and the Record Seperator is AM from which the record is seperated .Now to process I have to make line sequential,and more over record length is not same it varies as per the input address,
AM1234563 John Murray 24 Old streeet old... (5 Replies)
Discussion started by: vakharia Mahesh
5 Replies
6. Shell Programming and Scripting
Hi,
Could someone please assist on a quick way of How to extract data from indexed files (ISAM files) maintained in an UNIX(AIX) server.The file data needs to be extracted in flat text file or CSV or excel format .
Usually we have programs in microfocus COBOL to extract data, but would like... (2 Replies)
Discussion started by: devina
2 Replies
7. UNIX for Dummies Questions & Answers
Hi ,
I am having 3 files as
FILE1
1
2
3
FILE2
4
5
6
FILE3
7
8
9
I want to merge thes file such that the resultnt file should be as (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
8. UNIX for Advanced & Expert Users
Hi,
I posted this over at Macnn and was redirected here... I'm not a unix programmer at all, but I have some backup if needed. Thanks in advance for any input.
Is there a command for the osX terminal that will list sequentially numbered groups of file as one line instead of individually,... (1 Reply)
Discussion started by: kentm
1 Replies
9. Programming
We have to convert a sequential file to a 80 char line sequential file (HP UX platform).The sequential file contains special characters. which after conversion of the file to line sequential are getting coverted into "new line" or "tab" and file is getting distorted. Is there any way to read these... (2 Replies)
Discussion started by: Rajeshsu
2 Replies
10. UNIX for Dummies Questions & Answers
Hi
I need to access files from a specific folder of a Linux system from an another Linux System Remotely.
I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility.
Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies
CLUSTER(7) PostgreSQL 9.2.7 Documentation CLUSTER(7)
NAME
CLUSTER - cluster a table according to an index
SYNOPSIS
CLUSTER [VERBOSE] table_name [ USING index_name ]
CLUSTER [VERBOSE]
DESCRIPTION
CLUSTER instructs PostgreSQL to cluster the table specified by table_name based on the index specified by index_name. The index must
already have been defined on table_name.
When a table is clustered, it is physically reordered based on the index information. Clustering is a one-time operation: when the table is
subsequently updated, the changes are not clustered. That is, no attempt is made to store new or updated rows according to their index
order. (If one wishes, one can periodically recluster by issuing the command again. Also, setting the table's FILLFACTOR storage parameter
to less than 100% can aid in preserving cluster ordering during updates, since updated rows are kept on the same page if enough space is
available there.)
When a table is clustered, PostgreSQL remembers which index it was clustered by. The form CLUSTER table_name reclusters the table using the
same index as before. You can also use the CLUSTER or SET WITHOUT CLUSTER forms of ALTER TABLE (ALTER_TABLE(7)) to set the index to be used
for future cluster operations, or to clear any previous setting.
CLUSTER without any parameter reclusters all the previously-clustered tables in the current database that the calling user owns, or all
such tables if called by a superuser. This form of CLUSTER cannot be executed inside a transaction block.
When a table is being clustered, an ACCESS EXCLUSIVE lock is acquired on it. This prevents any other database operations (both reads and
writes) from operating on the table until the CLUSTER is finished.
PARAMETERS
table_name
The name (possibly schema-qualified) of a table.
index_name
The name of an index.
VERBOSE
Prints a progress report as each table is clustered.
NOTES
In cases where you are accessing single rows randomly within a table, the actual order of the data in the table is unimportant. However, if
you tend to access some data more than others, and there is an index that groups them together, you will benefit from using CLUSTER. If you
are requesting a range of indexed values from a table, or a single indexed value that has multiple rows that match, CLUSTER will help
because once the index identifies the table page for the first row that matches, all other rows that match are probably already on the same
table page, and so you save disk accesses and speed up the query.
CLUSTER can re-sort the table using either an index scan on the specified index, or (if the index is a b-tree) a sequential scan followed
by sorting. It will attempt to choose the method that will be faster, based on planner cost parameters and available statistical
information.
When an index scan is used, a temporary copy of the table is created that contains the table data in the index order. Temporary copies of
each index on the table are created as well. Therefore, you need free space on disk at least equal to the sum of the table size and the
index sizes.
When a sequential scan and sort is used, a temporary sort file is also created, so that the peak temporary space requirement is as much as
double the table size, plus the index sizes. This method is often faster than the index scan method, but if the disk space requirement is
intolerable, you can disable this choice by temporarily setting enable_sort to off.
It is advisable to set maintenance_work_mem to a reasonably large value (but not more than the amount of RAM you can dedicate to the
CLUSTER operation) before clustering.
Because the planner records statistics about the ordering of tables, it is advisable to run ANALYZE(7) on the newly clustered table.
Otherwise, the planner might make poor choices of query plans.
Because CLUSTER remembers which indexes are clustered, one can cluster the tables one wants clustered manually the first time, then set up
a periodic maintenance script that executes CLUSTER without any parameters, so that the desired tables are periodically reclustered.
EXAMPLES
Cluster the table employees on the basis of its index employees_ind:
CLUSTER employees USING employees_ind;
Cluster the employees table using the same index that was used before:
CLUSTER employees;
Cluster all tables in the database that have previously been clustered:
CLUSTER;
COMPATIBILITY
There is no CLUSTER statement in the SQL standard.
The syntax
CLUSTER index_name ON table_name
is also supported for compatibility with pre-8.3 PostgreSQL versions.
SEE ALSO
clusterdb(1)
PostgreSQL 9.2.7 2014-02-17 CLUSTER(7)