Ggil의 끄적끄적

4년전 집을 구하던 당시 그쪽 주위에는 2000만원 전후의 빌라 전세가 매우 많았고 그중에서 한곳을 선택하였습니다.

그집이 이미 ??은행에 근저당이 설정되어 있는 상태라서 제가 취할 수 있는 최고의 선택은 소액임대차보호법으로 전세금을 최대한 보증하면서 가장 깨끗하고 넒고 좋은 집을 선택하였고 그집이 바로 지난번에 살던 그집입니다.

저는 해당 집의 대리인과 계약을 하였습니다.

대리인은 집주인의 인감과 인감증명서를 보유하였고 절차상 아무런 문제가 없었습니다.

하지만 저는 안전한 부동산 계약을 위해서 복덕방을 중간에 껴서 계약을 하였고 공제증서를 받아두었습니다.

하지만 웬걸요.. 결국 전세집에 입주하고 3개월만에 집은 결국 경매에 붙여졌고 약 3년 7개월만에 새로운 집주인이 나타났습니다.

저는 전세금에서 소액임대차보호법에 의거한 1차 배당금을 받았습니다.

그리고 나머지 100만원에 대한 일반채권을 행사하기 위해서 법원에 소액소송을 걸었습니다.

아침일찍부터 기사분께서 오셔서 부산스럽게 설치를 하셨습니다.

설치가 다 끝난후 보란듯이 회사 인터넷 속도를 측정하였습니다.

다운로드 89Mbps, 업로드 1.75Mbps.

"어랏? 아저씨 업로드 속도가 왜 이래요?"

"고객님 저희 유선망은 업로드속도가 모든 서비스가 2메가로 제한되어있어요."

그냥 그러려니 했다. 그런가보다.

오전 10시쯤에 측정했을때의 수치 입니다.

그럼 오후 10시 쯤은 어떨까?

결과는 들쑥 날쑥입니다. 어떨때는 80Mbps 가까이 나오고 어떨땐 50Mbps 정도 나오더군요. 방금은 또 32Mbps 가 나오네요..... (예전에 메가페스 FTTH 망을 쓸땐 항상 90Mbps 가 유지되었습니다.)

속도가 아주 들쑥날쑥합니다.

그럼 지역망 전용 속도 측정이 아닌. 공신력 있는 측정기관은 어떨까요?

밴치비 : 26Mbps , 24.4Mbps , 26.6Mbps
한국정보사회진흥원 : 26Mbps , 31.7Mbps
마이스피드 : 50Mbps , 54.5Mbps , 39.6Mbps

보시다시피 들쑥날쑥입니다.

여기서 또 의심병이 발동했습니다.

의문점 : 왜 지역망은 속도가 높게 나오고 나머지 사설/공설 기관의 속도는 낮게 나올까?

가설1 : 지역망 -> 백본 의 속도가 구리다.
가설2 : 지역망 속도측정 프로그램이 거짓이다.

여기에서 가설2에 대한 확인을 위해 무식한 방법을 사용해봤습니다.


<지역망 속도측정>

스샷 몇개

Screenshot: 0.6.0: Color chooser

Screenshot: PDF mode

Screenshot: Custom controls menu

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell

14.2.2 ALTER TABLE Syntax

ALTER [IGNORE] TABLE tbl_name
    alter_specification [, alter_specification] ...

alter_specification:
    ADD [COLUMN] column_definition [FIRST | AFTER col_name ]
  | ADD [COLUMN] (column_definition,...)
  | ADD INDEX [index_name] [index_type] (index_col_name,...)
  | ADD [CONSTRAINT [symbol]]
        PRIMARY KEY [index_type] (index_col_name,...)
  | ADD [CONSTRAINT [symbol]]
        UNIQUE [index_name] [index_type] (index_col_name,...)
  | ADD [FULLTEXT|SPATIAL] [index_name] (index_col_name,...)
  | ADD [CONSTRAINT [symbol]]
        FOREIGN KEY [index_name] (index_col_name,...)
        [reference_definition]
  | ALTER [COLUMN] col_name {SET DEFAULT literal | DROP DEFAULT}
  | CHANGE [COLUMN] old_col_name column_definition
        [FIRST|AFTER col_name]
  | MODIFY [COLUMN] column_definition [FIRST | AFTER col_name]
  | DROP [COLUMN] col_name
  | DROP PRIMARY KEY
  | DROP INDEX index_name
  | DROP FOREIGN KEY fk_symbol
  | DISABLE KEYS
  | ENABLE KEYS
  | RENAME [TO] new_tbl_name
  | ORDER BY col_name
  | CONVERT TO CHARACTER SET charset_name [COLLATE collation_name]
  | [DEFAULT] CHARACTER SET charset_name [COLLATE collation_name]
  | DISCARD TABLESPACE
  | IMPORT TABLESPACE
  | table_options

ALTER TABLE allows you to change the structure of an existing table. For example, you can add or delete columns, create or destroy indexes, change the type of existing columns, or rename columns or the table itself. You can also change the comment for the table and type of the table.

The syntax for many of the allowable alterations is similar to clauses of the CREATE TABLE statement. See section 14.2.5 CREATE TABLE Syntax.

If you use ALTER TABLE to change a column specification but DESCRIBE tbl_name indicates that your column was not changed, it is possible that MySQL ignored your modification for one of the reasons described in section 14.2.5.1 Silent Column Specification Changes. For example, if you try to change a VARCHAR column to CHAR, MySQL will still use VARCHAR if the table contains other variable-length columns.

ALTER TABLE works by making a temporary copy of the original table. The alteration is performed on the copy, then the original table is deleted and the new one is renamed. While ALTER TABLE is executing, the original table is readable by other clients. Updates and writes to the table are stalled until the new table is ready, then are automatically redirected to the new table without any failed updates.

Note that if you use any other option to ALTER TABLE than RENAME, MySQL always creates a temporary table, even if the data wouldn't strictly need to be copied (such as when you change the name of a column). We plan to fix this in the future, but because ALTER TABLE is not a statement that is normally used frequently, this isn't high on our TODO list. For MyISAM tables, you can speed up the index re-creation operation (which is the slowest part of the alteration process) by setting the myisam_sort_buffer_size system variable to a high value.

• To use ALTER TABLE, you need ALTER, INSERT, and CREATE privileges for the table.
• IGNORE is a MySQL extension to standard SQL. It controls how ALTER TABLE works if there are duplicates on unique keys in the new table. If IGNORE isn't specified, the copy is aborted and rolled back if duplicate-key errors occur. If IGNORE is specified, then for rows with duplicates on a unique key, only the first row is used. The others are deleted.
• You can issue multiple ADD, ALTER, DROP, and CHANGE clauses in a single ALTER TABLE statement. This is a MySQL extension to standard SQL, which allows only one of each clause per ALTER TABLE statement. For example, to drop multiple columns in a single statement:

  mysql> ALTER TABLE t2 DROP COLUMN c, DROP COLUMN d;
  

• CHANGE col_name, DROP col_name, and DROP INDEX are MySQL extensions to standard SQL.
• MODIFY is an Oracle extension to ALTER TABLE.
• The word COLUMN is purely optional and can be omitted.
• If you use ALTER TABLE tbl_name RENAME TO new_tbl_name without any other options, MySQL simply renames any files that correspond to the table tbl_name. There is no need to create a temporary table. (You can also use the RENAME TABLE statement to rename tables. See section 14.2.9 RENAME TABLE Syntax.)
• column_definition clauses use the same syntax for ADD and CHANGE as for CREATE TABLE. Note that this syntax includes the column name, not just the column type. See section 14.2.5 CREATE TABLE Syntax.
• You can rename a column using a CHANGE old_col_name column_definition clause. To do so, specify the old and new column names and the type that the column currently has. For example, to rename an INTEGER column from a to b, you can do this:

  mysql> ALTER TABLE t1 CHANGE a b INTEGER;
  

  If you want to change a column's type but not the name, CHANGE syntax still requires an old and new column name, even if they are the same. For example:

  mysql> ALTER TABLE t1 CHANGE b b BIGINT NOT NULL;
  

  However, as of MySQL 3.22.16a, you can also use MODIFY to change a column's type without renaming it:

  mysql> ALTER TABLE t1 MODIFY b BIGINT NOT NULL;
  

• If you use CHANGE or MODIFY to shorten a column for which an index exists on part of the column (for example, if you have an index on the first 10 characters of a VARCHAR column), you cannot make the column shorter than the number of characters that are indexed.
• When you change a column type using CHANGE or MODIFY, MySQL tries to convert existing column values to the new type as well as possible.
• In MySQL 3.22 or later, you can use FIRST or AFTER col_name to add a column at a specific position within a table row. The default is to add the column last. From MySQL 4.0.1 on, you can also use FIRST and AFTER in CHANGE or MODIFY operations.
• ALTER COLUMN specifies a new default value for a column or removes the old default value. If the old default is removed and the column can be NULL, the new default is NULL. If the column cannot be NULL, MySQL assigns a default value, as described in section 14.2.5 CREATE TABLE Syntax.
• DROP INDEX removes an index. This is a MySQL extension to standard SQL. See section 14.2.7 DROP INDEX Syntax.
• If columns are dropped from a table, the columns are also removed from any index of which they are a part. If all columns that make up an index are dropped, the index is dropped as well.
• If a table contains only one column, the column cannot be dropped. If what you intend is to remove the table, use DROP TABLE instead.
• DROP PRIMARY KEY drops the primary index. (Prior to MySQL 4.1.2, if no primary index exists, DROP PRIMARY KEY drops the first UNIQUE index in the table. MySQL marks the first UNIQUE key as the PRIMARY KEY if no PRIMARY KEY was specified explicitly.) If you add a UNIQUE INDEX or PRIMARY KEY to a table, it is stored before any non-unique index so that MySQL can detect duplicate keys as early as possible.
• ORDER BY allows you to create the new table with the rows in a specific order. Note that the table will not remain in this order after inserts and deletes. This option is mainly useful when you know that you are mostly going to query the rows in a certain order; by using this option after big changes to the table, you might be able to get higher performance. In some cases, it might make sorting easier for MySQL if the table is in order by the column that you want to order it by later.
• If you use ALTER TABLE on a MyISAM table, all non-unique indexes are created in a separate batch (as for REPAIR TABLE). This should make ALTER TABLE much faster when you have many indexes. As of MySQL 4.0, this feature can be activated explicitly. ALTER TABLE ... DISABLE KEYS tells MySQL to stop updating non-unique indexes for a MyISAM table. ALTER TABLE ... ENABLE KEYS then should be used to re-create missing indexes. MySQL does this with a special algorithm that is much faster than inserting keys one by one, so disabling keys before performing bulk insert operations should give a considerable speedup. Using ALTER TABLE ... DISABLE KEYS will require the INDEX privilege in addition to the privileges mentioned earlier.
• The FOREIGN KEY and REFERENCES clauses are supported by the InnoDB storage engine, which implements ADD [CONSTRAINT [symbol]] FOREIGN KEY (...) REFERENCES ... (...). See section 16.7.4 FOREIGN KEY Constraints. For other storage engines, the clauses are parsed but ignored. The CHECK clause is parsed but ignored by all storage engines. See section 14.2.5 CREATE TABLE Syntax. The reason for accepting but ignoring syntax clauses is for compatibility, to make it easier to port code from other SQL servers, and to run applications that create tables with references. See section 1.8.5 MySQL Differences from Standard SQL.
• Starting from MySQL 4.0.13, InnoDB supports the use of ALTER TABLE to drop foreign keys:

  ALTER TABLE yourtablename DROP FOREIGN KEY fk_symbol;
  

  For more information, see section 16.7.4 FOREIGN KEY Constraints.
• ALTER TABLE ignores the DATA DIRECTORY and INDEX DIRECTORY table options.
• From MySQL 4.1.2 on, if you want to change all character columns (CHAR, VARCHAR, TEXT) to a new character set, use a statement like this:

  ALTER TABLE tbl_name CONVERT TO CHARACTER SET charset_name;
  

  This is useful, for example, after upgrading from MySQL 4.0.x to 4.1.x. See section 11.10 Upgrading Character Sets from MySQL 4.0. Warning: The preceding operation will convert column values between the character sets. This is not what you want if you have a column in one character set (like latin1) but the stored values actually use some other, incompatible character set (like utf8). In this case, you have to do the following for each such column:

  ALTER TABLE t1 CHANGE c1 c1 BLOB;
  ALTER TABLE t1 CHANGE c1 c1 TEXT CHARACTER SET utf8;
  

  The reason this works is that there is no conversion when you convert to or from BLOB columns. To change only the default character set for a table, use this statement:

  ALTER TABLE tbl_name DEFAULT CHARACTER SET charset_name;
  

  The word DEFAULT is optional. The default character set is the character set that is used if you don't specify the character set for a new column you add to a table (for example, with ALTER TABLE ... ADD column). Warning: From MySQL 4.1.2 and up, ALTER TABLE ... DEFAULT CHARACTER SET and ALTER TABLE ... CHARACTER SET are equivalent and change only the default table character set. In MySQL 4.1 releases before 4.1.2, ALTER TABLE ... DEFAULT CHARACTER SET changes the default character set, but ALTER TABLE ... CHARACTER SET (without DEFAULT) changes the default character set and also converts all columns to the new character set.
• For an InnoDB table that is created with its own tablespace in an `.ibd' file, that file can be discarded and imported. To discard the `.ibd' file, use this statement:

  ALTER TABLE tbl_name DISCARD TABLESPACE;
  

  This deletes the current `.ibd' file, so be sure that you have a backup first. Attempting to access the table while the tablespace file is discarded results in an error. To import the backup `.ibd' file back into the table, copy it into the database directory, then issue this statement:

  ALTER TABLE tbl_name IMPORT TABLESPACE;
  

  See section 16.7.6 Using Per-Table Tablespaces.
• With the mysql_info() C API function, you can find out how many records were copied, and (when IGNORE is used) how many records were deleted due to duplication of unique key values. See section 21.2.3.30 mysql_info().

Here are some examples that show uses of ALTER TABLE. Begin with a table t1 that is created as shown here:

mysql> CREATE TABLE t1 (a INTEGER,b CHAR(10));

To rename the table from t1 to t2:

mysql> ALTER TABLE t1 RENAME t2;

To change column a from INTEGER to TINYINT NOT NULL (leaving the name the same), and to change column b from CHAR(10) to CHAR(20) as well as renaming it from b to c:

mysql> ALTER TABLE t2 MODIFY a TINYINT NOT NULL, CHANGE b c CHAR(20);

To add a new TIMESTAMP column named d:

mysql> ALTER TABLE t2 ADD d TIMESTAMP;

To add indexes on column d and on column a:

mysql> ALTER TABLE t2 ADD INDEX (d), ADD INDEX (a);

To remove column c:

mysql> ALTER TABLE t2 DROP COLUMN c;

To add a new AUTO_INCREMENT integer column named c:

mysql> ALTER TABLE t2 ADD c INT UNSIGNED NOT NULL AUTO_INCREMENT,
    ->     ADD PRIMARY KEY (c);

Note that we indexed c (as a PRIMARY KEY), because AUTO_INCREMENT columns must be indexed, and also that we declare c as NOT NULL, because primary key columns cannot be NULL.

When you add an AUTO_INCREMENT column, column values are filled in with sequence numbers for you automatically. For MyISAM tables, you can set the first sequence number by executing SET INSERT_ID=value before ALTER TABLE or by using the AUTO_INCREMENT=value table option. See section 14.5.3.1 SET Syntax.

With MyISAM tables, if you don't change the AUTO_INCREMENT column, the sequence number will not be affected. If you drop an AUTO_INCREMENT column and then add another AUTO_INCREMENT column, the numbers are resequenced beginning with 1.

See section A.7.1 Problems with ALTER TABLE.

+-------+------------------+------+-----+---------+-------+
| Field | Type             | Null | Key | Default | Extra |
+-------+------------------+------+-----+---------+-------+
| ID    | int(10) unsigned | YES  |     | NULL    |       |
+-------+------------------+------+-----+---------+-------+