Revision 13296
Added by Aaron Marcuse-Kubitza over 10 years ago
index.htm | ||
---|---|---|
34 | 34 |
<DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegCore" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegCore" ADD_DATE="1354727779" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" style="margin-right: 0.5em;"/>VegCore</A><a name="__VegCore" href="#__VegCore" style="margin-left: 0.5em;">¶</a> |
35 | 35 |
<DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_schema" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_schema" ADD_DATE="1344469303" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" style="margin-right: 0.5em;"/>VegBIEN</A><a name="__VegBIEN" href="#__VegBIEN" style="margin-left: 0.5em;">¶</a> |
36 | 36 |
<DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_FAQ" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_FAQ" ADD_DATE="1389803305" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" style="margin-right: 0.5em;"/>FAQ</A><a name="__FAQ" href="#__FAQ" style="margin-left: 0.5em;">¶</a> |
37 |
<DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" name="__http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" ADD_DATE="1362008923" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png" style="margin-right: 0.5em;"/>vegbiendev</A><a name="__vegbiendev" href="#__vegbiendev" style="margin-left: 0.5em;">¶</a>
|
|
37 |
<DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" name="__http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" ADD_DATE="1362008923" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Favicon.ico"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Favicon.ico" style="margin-right: 0.5em;"/>vegbiendev</A><a name="__vegbiendev" href="#__vegbiendev" style="margin-left: 0.5em;">¶</a>
|
|
38 | 38 |
<DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/" name="__http://vegbiendev.nceas.ucsb.edu/phpmyadmin/" ADD_DATE="1361027615" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/favicon.ico"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/favicon.ico" style="margin-right: 0.5em;"/>"</A><a name="__"" href="#__"" style="margin-left: 0.5em;">¶</a> |
39 | 39 |
<DT><A HREF="http://nimoy.nceas.ucsb.edu/phpmyadmin/" name="__http://nimoy.nceas.ucsb.edu/phpmyadmin/" ADD_DATE="1318544417" ICON_URI="http://nimoy.nceas.ucsb.edu/phpmyadmin/favicon.ico"><img width="16" height="16" src="http://nimoy.nceas.ucsb.edu/phpmyadmin/favicon.ico" style="margin-right: 0.5em;"/>nimoy</A><a name="__nimoy" href="#__nimoy" style="margin-left: 0.5em;">¶</a> |
40 | 40 |
<DT><A HREF="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/redirect.php?subject=schema&server=%3A5432%3Aallow&database=vegbien&schema=public&" name="__http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/redirect.php?subject=schema&server=%3A5432%3Aallow&database=vegbien&schema=public&" ADD_DATE="1362008964" ICON_URI="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/images/themes/default/Introduction.png"><img width="16" height="16" src="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/images/themes/default/Introduction.png" style="margin-right: 0.5em;"/>starscream</A><a name="__starscream" href="#__starscream" style="margin-left: 0.5em;">¶</a> |
... | ... | |
687 | 687 |
</DL><p> |
688 | 688 |
<DT><a name="PostgreSQL" href="#PostgreSQL"><H3 ADD_DATE="1333386475">PostgreSQL</H3></a> |
689 | 689 |
<DL><p> |
690 |
<DT><a name="* TIDs" href="#* TIDs"><H3 ADD_DATE="1394183336">* TIDs</H3></a> |
|
691 |
<DL><p> |
|
692 |
<DT><A HREF="http://postgresql.1045698.n5.nabble.com/Using-ctid-column-changes-plan-drastically-td5717711.html" name="http://postgresql.1045698.n5.nabble.com/Using-ctid-column-changes-plan-drastically-td5717711.html" ADD_DATE="1394185828" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL - performance - Using ctid column changes plan drastically</A><a name="PostgreSQL - performance - Using ctid column changes plan drastically" href="#PostgreSQL - performance - Using ctid column changes plan drastically" style="margin-left: 0.5em;">¶</a> |
|
693 |
<DD>page's self-description: Using ctid column changes plan drastically. Hi, I was testing a query to delete duplicates to see how well using ctid works if the table doesn't have a unique identifier available. The table... |
|
694 |
|
|
695 |
"Joins on tid columns just aren't supported very well at the moment. [...] There are gotchas if any of the rows receive concurrent updates." (Tom Lane) |
|
696 |
|
|
697 |
"type tid doesn't have any hash support" (Tom Lane) |
|
698 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/ddl-system-columns.html" name="http://www.postgresql.org/docs/9.3/static/ddl-system-columns.html" ADD_DATE="1394185064" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: System Columns</A><a name="PostgreSQL: Documentation: 9.3: System Columns" href="#PostgreSQL: Documentation: 9.3: System Columns" style="margin-left: 0.5em;">¶</a> |
|
699 |
<DD>"ctid |
|
700 |
The physical location of the row version within its table. Note that although the ctid can be used to locate the row version very quickly, a row's ctid will change if it is updated or moved by VACUUM FULL. Therefore ctid is useless as a long-term row identifier [unless your DB is select-optimized and rarely updated]. The OID, or even better a user-defined serial number, should be used to identify logical rows." |
|
701 |
<DT><A HREF="http://www.postgresql.org/message-id/200206031717.g53HHLs03112@saturn.janwieck.net" name="http://www.postgresql.org/message-id/200206031717.g53HHLs03112@saturn.janwieck.net" ADD_DATE="1394183279" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: tid scan - is it ever used?</A><a name="Re: tid scan - is it ever used?" href="#Re: tid scan - is it ever used?" style="margin-left: 0.5em;">¶</a> |
|
702 |
<DD>" |
|
703 |
Currently it is the fastest possible access to a single row. |
|
704 |
So an application that selects data and wants to update rows |
|
705 |
is optimized for PostgreSQL if it knows about that fact and |
|
706 |
qualifies the updates by ctid. |
|
707 |
" |
|
708 |
<DT><A HREF="http://www.postgresql.org/message-id/1031147457.3339.12.camel@taru.tm.ee" name="http://www.postgresql.org/message-id/1031147457.3339.12.camel@taru.tm.ee" ADD_DATE="1394183324" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: What is Tid Scan</A><a name="Re: What is Tid Scan" href="#Re: What is Tid Scan" style="margin-left: 0.5em;">¶</a> |
|
709 |
<DD>"It is scanning table by TupleID's. A tuple id is a 6-byte entity which |
|
710 |
consists of 4-byte page number and 2-byte tuple index inside page. |
|
711 |
|
|
712 |
So if you know the TID you can directly get the corresponding tuple." |
|
713 |
<DT><A HREF="http://blog.2ndquadrant.com/using_the_postgresql_system_co/" name="http://blog.2ndquadrant.com/using_the_postgresql_system_co/" ADD_DATE="1394186108" ICON_URI="http://blog.2ndquadrant.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://blog.2ndquadrant.com/favicon.ico" style="margin-right: 0.5em;"/>Using the PostgreSQL System Columns | 2ndQuadrant</A><a name="Using the PostgreSQL System Columns | 2ndQuadrant" href="#Using the PostgreSQL System Columns | 2ndQuadrant" style="margin-left: 0.5em;">¶</a> |
|
714 |
<DD>"One thing you can use these for is finding duplicate data in a table. Let’s say you’re trying to add a unique constraint, but one row in the table is duplicated 3 times, which blocks the unique index from being created. When rows are identical in every column, you can’t write any simple SELECT statement to uniquely identify them. That means deleting all of them but one copy requires some annoying and fragile SQL code, combining DELETE with LIMIT and/or OFFSET–which is always scary. If you use the ctid instead, the implementation will be PostgreSQL specific, but it will also be faster and cleaner. See Deleting Duplicate Records in a Table for an example of how that can be done." |
|
715 |
</DL><p> |
|
716 | 690 |
<DT><a name="backups" href="#backups"><H3 ADD_DATE="1397769882">backups</H3></a> |
717 | 691 |
<DD>online backups: |
718 | 692 |
|
719 | 693 |
pg_start_backup() method: |
720 |
(more reliable, but requires putting the DB server into a special mode during backup) |
|
694 |
(more reliable and Postgres-recommended, but requires putting the DB server into a special mode during backup)
|
|
721 | 695 |
# configure: |
722 | 696 |
## in postgresql.conf, set wal_level = hot_standby |
723 | 697 |
## $ sudo service postgresql restart |
... | ... | |
775 | 749 |
not be capable of replaying whatever happened since your last checkpoint." |
776 | 750 |
<DT><A HREF="http://www.postgresql.org/message-id/CB0FB369FF86E248A884BCC002562BCB010C0D9F@pisgsna01sxch01.ana.firstamdata.com" name="http://www.postgresql.org/message-id/CB0FB369FF86E248A884BCC002562BCB010C0D9F@pisgsna01sxch01.ana.firstamdata.com" ADD_DATE="1397777667" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: what are the pg_clog and pg_xlog directories ?</A><a name="Re: what are the pg_clog and pg_xlog directories ?" href="#Re: what are the pg_clog and pg_xlog directories ?" style="margin-left: 0.5em;">¶</a> |
777 | 751 |
</DL><p> |
752 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/continuous-archiving.html" name="http://www.postgresql.org/docs/9.3/static/continuous-archiving.html" ADD_DATE="1397776277" ICON_URI="http://www.postgresql.org/favicon.ico"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)</A><a name="** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)" href="#** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)" style="margin-left: 0.5em;">¶</a> |
|
753 |
<DD>"To prepare for low level standalone hot backups, set wal_level to archive (or hot_standby), archive_mode to on, and set up an archive_command that performs archiving only when a switch file exists." |
|
754 |
|
|
755 |
"When wal_level is minimal some SQL commands are optimized to avoid WAL logging" this is really the only reason that wal_level must be archive, since the server normally keeps around lots of WAL segments anyway. |
|
756 |
|
|
757 |
"The file identified by pg_stop_backup's result is the last segment that is required to form a complete set of backup files" |
|
758 |
* actually, this is only needed if parts of base/ were copied *after* the backup finishes copying pg_xlog/. most backup mechanisms copy in alphabetical order, so that pg_xlog/ will be the last subdir copied, and the last segment in it will be copied after base/ is already done. |
|
778 | 759 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-wal.html" name="http://www.postgresql.org/docs/9.3/static/runtime-config-wal.html" ADD_DATE="1397779174" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>** PostgreSQL: Documentation: 9.3: Write Ahead Log</A><a name="** PostgreSQL: Documentation: 9.3: Write Ahead Log" href="#** PostgreSQL: Documentation: 9.3: Write Ahead Log" style="margin-left: 0.5em;">¶</a> |
779 | 760 |
<DD>"But minimal WAL does not contain enough information to reconstruct the data from a base backup and the WAL logs, so either archive or hot_standby level must be used to enable WAL archiving (archive_mode) and streaming replication." |
780 | 761 |
|
... | ... | |
784 | 765 |
** note that turning fsync on protects against power failure, but not hard disk failure or human error. for that, you need continuous archiving or point-in-time recovery, respectively. |
785 | 766 |
|
786 | 767 |
"In hot_standby level, the same information is logged as with archive, plus information needed to reconstruct the status of running transactions from the WAL. [...] It is thought that there is little measurable difference in performance between using hot_standby and archive levels" ie, if you are going to use archive anyway, might as well go straight to hot_standby |
787 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/continuous-archiving.html" name="http://www.postgresql.org/docs/9.3/static/continuous-archiving.html" ADD_DATE="1397776277" ICON_URI="http://www.postgresql.org/favicon.ico"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>*** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)</A><a name="*** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)" href="#*** PostgreSQL: Documentation: 9.3: Continuous Archiving and Point-in-Time Recovery (PITR)" style="margin-left: 0.5em;">¶</a> |
|
788 |
<DD>"To prepare for low level standalone hot backups, set wal_level to archive (or hot_standby), archive_mode to on, and set up an archive_command that performs archiving only when a switch file exists." |
|
768 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/backup-file.html" name="http://www.postgresql.org/docs/9.3/static/backup-file.html" ADD_DATE="1397776134" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>*** PostgreSQL: Documentation: 9.3: File System Level Backup</A><a name="*** PostgreSQL: Documentation: 9.3: File System Level Backup" href="#*** PostgreSQL: Documentation: 9.3: File System Level Backup" style="margin-left: 0.5em;">¶</a> |
|
769 |
<DD>"The database server must be shut down in order to get a usable backup. Half-way measures such as disallowing all connections will not work (in part [...] because of internal buffering within the server)." |
|
770 |
** in practice, this is not necessarily the case. it is entirely possible to get a usable filesystem-level backup, using the approaches described at http://vegpath.org/links/#backups . |
|
771 |
this is important because filesystem-level backups have several significant advantages over traditional database-level backups with pg_dump: |
|
772 |
1) only changed files will be backed up each time, rather than the entire database |
|
773 |
2) no CPU time needs to be spent on intensive compression of the data |
|
774 |
3) most importantly, the backup is instantaneously restorable simply by swapping the backup and primary database directories. by comparison, a pg_dump backup can take many hours to restore. |
|
789 | 775 |
|
790 |
to work with a filesystem-level backup, you need a WAL chain that's at least long enough (time-wise) for the WAL blocks created when it starts copying base/ to still be around when it finishes copying pg_xlog/ (it must also copy in alphabetical order, and not in parallel).
|
|
776 |
in general, to get a consistent filesystem-level backup, you need a WAL chain that's at least long enough (time-wise) for the WAL blocks created when it starts copying base/ to still be around when it finishes copying pg_xlog/ (it must also copy in alphabetical order, and not in parallel)
|
|
791 | 777 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-replication.html#GUC-WAL-KEEP-SEGMENTS" name="http://www.postgresql.org/docs/9.3/static/runtime-config-replication.html#GUC-WAL-KEEP-SEGMENTS" ADD_DATE="1398234626" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>*** PostgreSQL: Documentation: 9.3: Replication: wal_keep_segments</A><a name="*** PostgreSQL: Documentation: 9.3: Replication: wal_keep_segments" href="#*** PostgreSQL: Documentation: 9.3: Replication: wal_keep_segments" style="margin-left: 0.5em;">¶</a> |
792 | 778 |
<DD>"wal_keep_segments (integer) |
793 | 779 |
|
... | ... | |
796 | 782 |
<DD>page's self-description: Postgres 9.3 feature highlight: parallel pg_dump |
797 | 783 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/sql-checkpoint.html" name="http://www.postgresql.org/docs/9.3/static/sql-checkpoint.html" ADD_DATE="1398205258" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: CHECKPOINT</A><a name="PostgreSQL: Documentation: 9.3: CHECKPOINT" href="#PostgreSQL: Documentation: 9.3: CHECKPOINT" style="margin-left: 0.5em;">¶</a> |
798 | 784 |
<DD>"A checkpoint is a point in the transaction log sequence at which all data files have been updated to reflect the information in the log" |
799 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/backup-file.html" name="http://www.postgresql.org/docs/9.3/static/backup-file.html" ADD_DATE="1397776134" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: File System Level Backup</A><a name="PostgreSQL: Documentation: 9.3: File System Level Backup" href="#PostgreSQL: Documentation: 9.3: File System Level Backup" style="margin-left: 0.5em;">¶</a> |
|
800 |
<DD>"The database server must be shut down in order to get a usable backup. Half-way measures such as disallowing all connections will not work (in part [...] because of internal buffering within the server)." |
|
801 |
** in practice, this is not necessarily the case. it is entirely possible to get a usable filesystem-level backup, using the approaches described at http://vegpath.org/links/#backups . |
|
802 |
this is important because filesystem-level backups have several significant advantages over traditional database-level backups with pg_dump: |
|
803 |
1) only changed files will be backed up each time, rather than the entire database |
|
804 |
2) no CPU time needs to be spent on intensive compression of the data |
|
805 |
3) most importantly, the backup is instantaneously restorable simply by swapping the backup and primary database directories. by comparison, a pg_dump backup can take many hours to restore. |
|
806 | 785 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/app-pgbasebackup.html" name="http://www.postgresql.org/docs/9.3/static/app-pgbasebackup.html" ADD_DATE="1397778881" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: pg_basebackup</A><a name="PostgreSQL: Documentation: 9.3: pg_basebackup" href="#PostgreSQL: Documentation: 9.3: pg_basebackup" style="margin-left: 0.5em;">¶</a> |
807 | 786 |
</DL><p> |
808 | 787 |
<DT><a name="disk space" href="#disk space"><H3 ADD_DATE="1340661986">disk space</H3></a> |
... | ... | |
828 | 807 |
</DL><p> |
829 | 808 |
<DT><a name="doc" href="#doc"><H3 ADD_DATE="1366152313">doc</H3></a> |
830 | 809 |
<DL><p> |
831 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" name="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" ADD_DATE="1393355422" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>** PostgreSQL: Documentation: 9.3: Function Volatility Categories</A><a name="** PostgreSQL: Documentation: 9.3: Function Volatility Categories" href="#** PostgreSQL: Documentation: 9.3: Function Volatility Categories" style="margin-left: 0.5em;">¶</a>
|
|
810 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/xfunc-volatility.html" name="http://www.postgresql.org/docs/9.3/static/xfunc-volatility.html" ADD_DATE="1393355422" ICON_URI="http://www.postgresql.org/favicon.ico"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>** PostgreSQL: Documentation: 9.3: Function Volatility Categories</A><a name="** PostgreSQL: Documentation: 9.3: Function Volatility Categories" href="#** PostgreSQL: Documentation: 9.3: Function Volatility Categories" style="margin-left: 0.5em;">¶</a>
|
|
832 | 811 |
<DD>- |
833 | 812 |
*** "A common error is to label a function IMMUTABLE when its results depend on a configuration parameter. For example, a function that manipulates timestamps might well have results that depend on the TimeZone setting. For safety, such functions should be labeled STABLE instead." |
834 | 813 |
this especially includes functions that depend on the search_path! (ie. that don't have schema qualifiers on all invoked functions.) however, this effect will only be noticeable if the function is called on only *constant* values in a *PL/pgSQL* function, in which case the wrong search_path (the one in effect at *create* time) will be used. |
... | ... | |
865 | 844 |
<DT><A HREF="http://www.postgresql.org/docs/8.3/static/sql-rollback-to.html" name="http://www.postgresql.org/docs/8.3/static/sql-rollback-to.html" ADD_DATE="1340398641" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.3: ROLLBACK TO SAVEPOINT</A><a name="PostgreSQL: Documentation: 8.3: ROLLBACK TO SAVEPOINT" href="#PostgreSQL: Documentation: 8.3: ROLLBACK TO SAVEPOINT" style="margin-left: 0.5em;">¶</a> |
866 | 845 |
<DT><A HREF="http://www.postgresql.org/docs/8.3/static/functions-comparisons.html" name="http://www.postgresql.org/docs/8.3/static/functions-comparisons.html" ADD_DATE="1351586419" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.3: Row and Array Comparisons</A><a name="PostgreSQL: Documentation: 8.3: Row and Array Comparisons" href="#PostgreSQL: Documentation: 8.3: Row and Array Comparisons" style="margin-left: 0.5em;">¶</a> |
867 | 846 |
<DT><A HREF="http://www.postgresql.org/docs/8.3/static/monitoring-stats.html" name="http://www.postgresql.org/docs/8.3/static/monitoring-stats.html" ADD_DATE="1338849024" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.3: The Statistics Collector</A><a name="PostgreSQL: Documentation: 8.3: The Statistics Collector" href="#PostgreSQL: Documentation: 8.3: The Statistics Collector" style="margin-left: 0.5em;">¶</a> |
868 |
<DT><A HREF="http://www.postgresql.org/docs/8.4/interactive/plpgsql-errors-and-messages.html" name="http://www.postgresql.org/docs/8.4/interactive/plpgsql-errors-and-messages.html" ADD_DATE="1343096314" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.4: Errors and Messages</A><a name="PostgreSQL: Documentation: 8.4: Errors and Messages" href="#PostgreSQL: Documentation: 8.4: Errors and Messages" style="margin-left: 0.5em;">¶</a> |
|
869 | 847 |
<DT><A HREF="http://www.postgresql.org/docs/8.4/static/xfunc-overload.html" name="http://www.postgresql.org/docs/8.4/static/xfunc-overload.html" ADD_DATE="1340247331" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.4: Function Overloading</A><a name="PostgreSQL: Documentation: 8.4: Function Overloading" href="#PostgreSQL: Documentation: 8.4: Function Overloading" style="margin-left: 0.5em;">¶</a> |
870 | 848 |
<DT><A HREF="http://www.postgresql.org/docs/8.4/static/xfunc-sql.html#XFUNC-SQL-VARIADIC-FUNCTIONS" name="http://www.postgresql.org/docs/8.4/static/xfunc-sql.html#XFUNC-SQL-VARIADIC-FUNCTIONS" ADD_DATE="1348017604" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.4: Query Language (SQL) Functions</A><a name="PostgreSQL: Documentation: 8.4: Query Language (SQL) Functions" href="#PostgreSQL: Documentation: 8.4: Query Language (SQL) Functions" style="margin-left: 0.5em;">¶</a> |
871 | 849 |
<DT><A HREF="http://www.postgresql.org/docs/8.4/static/queries-with.html" name="http://www.postgresql.org/docs/8.4/static/queries-with.html" ADD_DATE="1357756970" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.4: WITH Queries (Common Table Expressions)</A><a name="PostgreSQL: Documentation: 8.4: WITH Queries (Common Table Expressions)" href="#PostgreSQL: Documentation: 8.4: WITH Queries (Common Table Expressions)" style="margin-left: 0.5em;">¶</a> |
... | ... | |
1052 | 1030 |
The OID of the table containing this row. This column is particularly handy for queries that select from inheritance hierarchies (see Section 5.8), since without it, it's difficult to tell which individual table a row came from. The tableoid can be joined against the oid column of pg_class to obtain the table name." |
1053 | 1031 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/sql-values.html" name="http://www.postgresql.org/docs/9.3/static/sql-values.html" ADD_DATE="1397021348" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: VALUES</A><a name="PostgreSQL: Documentation: 9.3: VALUES" href="#PostgreSQL: Documentation: 9.3: VALUES" style="margin-left: 0.5em;">¶</a> |
1054 | 1032 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/queries-values.html" name="http://www.postgresql.org/docs/9.3/static/queries-values.html" ADD_DATE="1397021338" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: VALUES Lists</A><a name="PostgreSQL: Documentation: 9.3: VALUES Lists" href="#PostgreSQL: Documentation: 9.3: VALUES Lists" style="margin-left: 0.5em;">¶</a> |
1033 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/queries-with.html" name="http://www.postgresql.org/docs/9.3/static/queries-with.html" ADD_DATE="1398240460" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: WITH Queries (Common Table Expressions)</A><a name="PostgreSQL: Documentation: 9.3: WITH Queries (Common Table Expressions)" href="#PostgreSQL: Documentation: 9.3: WITH Queries (Common Table Expressions)" style="margin-left: 0.5em;">¶</a> |
|
1055 | 1034 |
<DT><A HREF="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" name="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" ADD_DATE="1333386461" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: Log File Maintenance</A><a name="PostgreSQL: Documentation: Manuals: Log File Maintenance" href="#PostgreSQL: Documentation: Manuals: Log File Maintenance" style="margin-left: 0.5em;">¶</a> |
1056 |
<DT><A HREF="http://www.postgresql.org/docs/9.1/interactive/index.html" name="http://www.postgresql.org/docs/9.1/interactive/index.html" ADD_DATE="1317673868" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation</A><a name="PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" href="#PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" style="margin-left: 0.5em;">¶</a> |
|
1057 | 1035 |
<DT><A HREF="http://www.postgresql.org/docs/8.3/static/app-psql.html" name="http://www.postgresql.org/docs/8.3/static/app-psql.html" ADD_DATE="1325722373" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: psql</A><a name="PostgreSQL: Documentation: Manuals: psql" href="#PostgreSQL: Documentation: Manuals: psql" style="margin-left: 0.5em;">¶</a> |
1058 | 1036 |
<DT><A HREF="http://www.postgresql.org/docs/8.3/static/functions-admin.html" name="http://www.postgresql.org/docs/8.3/static/functions-admin.html" ADD_DATE="1336443290" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: System Administration Functions</A><a name="PostgreSQL: Documentation: Manuals: System Administration Functions" href="#PostgreSQL: Documentation: Manuals: System Administration Functions" style="margin-left: 0.5em;">¶</a> |
1059 | 1037 |
<DT><A HREF="http://www.postgresql.org/docs/8.1/static/manage-ag-templatedbs.html" name="http://www.postgresql.org/docs/8.1/static/manage-ag-templatedbs.html" ADD_DATE="1335056156" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: Template Databases</A><a name="PostgreSQL: Documentation: Manuals: Template Databases" href="#PostgreSQL: Documentation: Manuals: Template Databases" style="margin-left: 0.5em;">¶</a> |
1060 |
<DT><A HREF="http://www.postgresql.org/docs/current/static/queries-with.html" name="http://www.postgresql.org/docs/current/static/queries-with.html" ADD_DATE="1332635517" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: WITH Queries (Common Table Expressions)</A><a name="PostgreSQL: Documentation: Manuals: WITH Queries (Common Table Expressions)" href="#PostgreSQL: Documentation: Manuals: WITH Queries (Common Table Expressions)" style="margin-left: 0.5em;">¶</a> |
|
1061 | 1038 |
</DL><p> |
1062 | 1039 |
<DT><a name="from/to MySQL" href="#from/to MySQL"><H3 ADD_DATE="1360831701">from/to MySQL</H3></a> |
1063 | 1040 |
<DL><p> |
... | ... | |
1271 | 1248 |
<DT><A HREF="http://www.postgresql.org/message-id/4811DC02.6030800@archonet.com" name="http://www.postgresql.org/message-id/4811DC02.6030800@archonet.com" ADD_DATE="1369925133" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: Last insert/update/delete time for a table</A><a name="Re: Last insert/update/delete time for a table" href="#Re: Last insert/update/delete time for a table" style="margin-left: 0.5em;">¶</a> |
1272 | 1249 |
<DT><A HREF="http://www.postgresql.org/message-id/3f0b79eb0804250725w3349903iedbe11f0e2cd3fe5@mail.gmail.com" name="http://www.postgresql.org/message-id/3f0b79eb0804250725w3349903iedbe11f0e2cd3fe5@mail.gmail.com" ADD_DATE="1369925149" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: Last insert/update/delete time for a table</A><a name="Re: Last insert/update/delete time for a table" href="#Re: Last insert/update/delete time for a table" style="margin-left: 0.5em;">¶</a> |
1273 | 1250 |
</DL><p> |
1251 |
<DT><a name="TIDs" href="#TIDs"><H3 ADD_DATE="1394183336">TIDs</H3></a> |
|
1252 |
<DL><p> |
|
1253 |
<DT><A HREF="http://postgresql.1045698.n5.nabble.com/Using-ctid-column-changes-plan-drastically-td5717711.html" name="http://postgresql.1045698.n5.nabble.com/Using-ctid-column-changes-plan-drastically-td5717711.html" ADD_DATE="1394185828" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL - performance - Using ctid column changes plan drastically</A><a name="PostgreSQL - performance - Using ctid column changes plan drastically" href="#PostgreSQL - performance - Using ctid column changes plan drastically" style="margin-left: 0.5em;">¶</a> |
|
1254 |
<DD>page's self-description: Using ctid column changes plan drastically. Hi, I was testing a query to delete duplicates to see how well using ctid works if the table doesn't have a unique identifier available. The table... |
|
1255 |
|
|
1256 |
"Joins on tid columns just aren't supported very well at the moment. [...] There are gotchas if any of the rows receive concurrent updates." (Tom Lane) |
|
1257 |
|
|
1258 |
"type tid doesn't have any hash support" (Tom Lane) |
|
1259 |
<DT><A HREF="http://www.postgresql.org/docs/9.3/static/ddl-system-columns.html" name="http://www.postgresql.org/docs/9.3/static/ddl-system-columns.html" ADD_DATE="1394185064" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: System Columns</A><a name="PostgreSQL: Documentation: 9.3: System Columns" href="#PostgreSQL: Documentation: 9.3: System Columns" style="margin-left: 0.5em;">¶</a> |
|
1260 |
<DD>"ctid |
|
1261 |
The physical location of the row version within its table. Note that although the ctid can be used to locate the row version very quickly, a row's ctid will change if it is updated or moved by VACUUM FULL. Therefore ctid is useless as a long-term row identifier [unless your DB is select-optimized and rarely updated]. The OID, or even better a user-defined serial number, should be used to identify logical rows." |
|
1262 |
<DT><A HREF="http://www.postgresql.org/message-id/200206031717.g53HHLs03112@saturn.janwieck.net" name="http://www.postgresql.org/message-id/200206031717.g53HHLs03112@saturn.janwieck.net" ADD_DATE="1394183279" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: tid scan - is it ever used?</A><a name="Re: tid scan - is it ever used?" href="#Re: tid scan - is it ever used?" style="margin-left: 0.5em;">¶</a> |
|
1263 |
<DD>" |
|
1264 |
Currently it is the fastest possible access to a single row. |
|
1265 |
So an application that selects data and wants to update rows |
|
1266 |
is optimized for PostgreSQL if it knows about that fact and |
|
1267 |
qualifies the updates by ctid. |
|
1268 |
" |
|
1269 |
<DT><A HREF="http://www.postgresql.org/message-id/1031147457.3339.12.camel@taru.tm.ee" name="http://www.postgresql.org/message-id/1031147457.3339.12.camel@taru.tm.ee" ADD_DATE="1394183324" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>Re: What is Tid Scan</A><a name="Re: What is Tid Scan" href="#Re: What is Tid Scan" style="margin-left: 0.5em;">¶</a> |
|
1270 |
<DD>"It is scanning table by TupleID's. A tuple id is a 6-byte entity which |
|
1271 |
consists of 4-byte page number and 2-byte tuple index inside page. |
|
1272 |
|
|
1273 |
So if you know the TID you can directly get the corresponding tuple." |
|
1274 |
<DT><A HREF="http://blog.2ndquadrant.com/using_the_postgresql_system_co/" name="http://blog.2ndquadrant.com/using_the_postgresql_system_co/" ADD_DATE="1394186108" ICON_URI="http://blog.2ndquadrant.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://blog.2ndquadrant.com/favicon.ico" style="margin-right: 0.5em;"/>Using the PostgreSQL System Columns | 2ndQuadrant</A><a name="Using the PostgreSQL System Columns | 2ndQuadrant" href="#Using the PostgreSQL System Columns | 2ndQuadrant" style="margin-left: 0.5em;">¶</a> |
|
1275 |
<DD>"One thing you can use these for is finding duplicate data in a table. Let’s say you’re trying to add a unique constraint, but one row in the table is duplicated 3 times, which blocks the unique index from being created. When rows are identical in every column, you can’t write any simple SELECT statement to uniquely identify them. That means deleting all of them but one copy requires some annoying and fragile SQL code, combining DELETE with LIMIT and/or OFFSET–which is always scary. If you use the ctid instead, the implementation will be PostgreSQL specific, but it will also be faster and cleaner. See Deleting Duplicate Records in a Table for an example of how that can be done." |
|
1276 |
</DL><p> |
|
1274 | 1277 |
<DT><a name="vacuuming" href="#vacuuming"><H3 ADD_DATE="1377911873">vacuuming</H3></a> |
1275 | 1278 |
<DL><p> |
1276 | 1279 |
<DT><A HREF="http://dba.stackexchange.com/questions/42040/how-to-monitor-or-do-vacuum-without-stop-all" name="http://dba.stackexchange.com/questions/42040/how-to-monitor-or-do-vacuum-without-stop-all" ADD_DATE="1394172285" ICON_URI="http://cdn.sstatic.net/dba/img/favicon.ico?v=a731663709aa" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://cdn.sstatic.net/dba/img/favicon.ico?v=a731663709aa" style="margin-right: 0.5em;"/>* postgresql - How to monitor or do vacuum without stop all? - Database Administrators Stack Exchange</A><a name="* postgresql - How to monitor or do vacuum without stop all? - Database Administrators Stack Exchange" href="#* postgresql - How to monitor or do vacuum without stop all? - Database Administrators Stack Exchange" style="margin-left: 0.5em;">¶</a> |
... | ... | |
1729 | 1732 |
<DL><p> |
1730 | 1733 |
<DT><a name="backups" href="#backups"><H3 ADD_DATE="1397769906">backups</H3></a> |
1731 | 1734 |
<DL><p> |
1735 |
<DT><A HREF="http://www.mikerubel.org/computers/rsync_snapshots/" name="http://www.mikerubel.org/computers/rsync_snapshots/" ADD_DATE="1398286506" ICON_URI="http://www.mikerubel.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.mikerubel.org/favicon.ico" style="margin-right: 0.5em;"/>Easy Automated Snapshot-Style Backups with Rsync</A><a name="Easy Automated Snapshot-Style Backups with Rsync" href="#Easy Automated Snapshot-Style Backups with Rsync" style="margin-left: 0.5em;">¶</a> |
|
1736 |
<DD>page's self-description: How to make easy, automated snapshot-style backups with rsync and UNIX |
|
1737 |
<DT><A HREF="http://www.linuxquestions.org/questions/linux-software-2/linux-equivalent-to-time-machine-889376/" name="http://www.linuxquestions.org/questions/linux-software-2/linux-equivalent-to-time-machine-889376/" ADD_DATE="1398286515" ICON_URI="http://www.linuxquestions.org/favicon.ico" LAST_CHARSET="windows-1252"><img width="16" height="16" src="http://www.linuxquestions.org/favicon.ico" style="margin-right: 0.5em;"/>Linux equivalent to "Time Machine"</A><a name="Linux equivalent to "Time Machine"" href="#Linux equivalent to "Time Machine"" style="margin-left: 0.5em;">¶</a> |
|
1738 |
<DD>page's self-description: Is there a polished and working equivilent to Mac's time machine? I've googled and found some of the alternatives, and installed them and used them, |
|
1739 |
|
|
1740 |
""Backintime" will work, but has a simple interface" |
|
1732 | 1741 |
<DT><A HREF="http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html" name="http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html" ADD_DATE="1397763219" ICON_URI="http://www.tldp.org/favicon.ico" LAST_CHARSET="windows-1252"><img width="16" height="16" src="http://www.tldp.org/favicon.ico" style="margin-right: 0.5em;"/>Taking a Backup Using Snapshots</A><a name="Taking a Backup Using Snapshots" href="#Taking a Backup Using Snapshots" style="margin-left: 0.5em;">¶</a> |
1733 | 1742 |
<DD>"A snapshot volume [...] presents all the data that was in the volume at the time the snapshot was created" |
1734 | 1743 |
</DL><p> |
... | ... | |
1752 | 1761 |
</DL><p> |
1753 | 1762 |
<DT><a name="Ubuntu" href="#Ubuntu"><H3 ADD_DATE="1373365250">Ubuntu</H3></a> |
1754 | 1763 |
<DL><p> |
1764 |
<DT><a name="Ubuntu 14.04 upgrade" href="#Ubuntu 14.04 upgrade"><H3 ADD_DATE="1398295125">Ubuntu 14.04 upgrade</H3></a> |
|
1765 |
<DL><p> |
|
1766 |
<DT><a name="Apache" href="#Apache"><H3 ADD_DATE="1398295165">Apache</H3></a> |
|
1767 |
<DD>**WARNING**: this breaks display of some pages, see https://projects.nceas.ucsb.edu/nceas/issues/903 |
|
1768 |
|
|
1769 |
after upgrading: |
|
1770 |
$ sudo a2dismod php5_cgi |
|
1771 |
$ sudo apache2ctl restart |
|
1772 |
</DD> |
|
1773 |
<DL><p> |
|
1774 |
</DL><p> |
|
1775 |
<DT><A HREF="http://itsfoss.com/things-to-do-after-installing-ubuntu-14-04/" name="http://itsfoss.com/things-to-do-after-installing-ubuntu-14-04/" ADD_DATE="1398211354" ICON_URI="http://itsfoss.com/wp-content/themes/focus-pro/images/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://itsfoss.com/wp-content/themes/focus-pro/images/favicon.ico" style="margin-right: 0.5em;"/>** 14 Things To Do After Installing Ubuntu 14.04</A><a name="** 14 Things To Do After Installing Ubuntu 14.04" href="#** 14 Things To Do After Installing Ubuntu 14.04" style="margin-left: 0.5em;">¶</a> |
|
1776 |
<DD>page's self-description: Confused what to do after Installing Ubuntu 14.04? Here are some essential things to do after installing Ubuntu 14.04 Trusty Tahr. |
|
1777 |
</DL><p> |
|
1755 | 1778 |
<DT><A HREF="http://ubuntuforums.org/showthread.php?t=1222909" name="http://ubuntuforums.org/showthread.php?t=1222909" ADD_DATE="1329253743" ICON_URI="http://ubuntuforums.org/favicon.ico" LAST_CHARSET="ISO-8859-1"><img width="16" height="16" src="http://ubuntuforums.org/favicon.ico" style="margin-right: 0.5em;"/>[ubuntu] On login 5 packages can be updated - Ubuntu Forums</A><a name="[ubuntu] On login 5 packages can be updated - Ubuntu Forums" href="#[ubuntu] On login 5 packages can be updated - Ubuntu Forums" style="margin-left: 0.5em;">¶</a> |
1756 | 1779 |
<DD>page's self-description: [ubuntu] On login 5 packages can be updated Server Platforms |
1757 | 1780 |
<DT><A HREF="http://ubuntuforums.org/showthread.php?t=2058377" name="http://ubuntuforums.org/showthread.php?t=2058377" ADD_DATE="1373365205" ICON_URI="http://ubuntuforums.org/favicon.ico" LAST_CHARSET="windows-1252"><img width="16" height="16" src="http://ubuntuforums.org/favicon.ico" style="margin-right: 0.5em;"/>[ubuntu] remove old linux kernels</A><a name="[ubuntu] remove old linux kernels" href="#[ubuntu] remove old linux kernels" style="margin-left: 0.5em;">¶</a> |
... | ... | |
1765 | 1788 |
sudo apt-get --purge remove <Kernel> |
1766 | 1789 |
sudo update-grub |
1767 | 1790 |
" |
1768 |
<DT><A HREF="http://itsfoss.com/things-to-do-after-installing-ubuntu-14-04/" name="http://itsfoss.com/things-to-do-after-installing-ubuntu-14-04/" ADD_DATE="1398211354" ICON_URI="http://itsfoss.com/wp-content/themes/focus-pro/images/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://itsfoss.com/wp-content/themes/focus-pro/images/favicon.ico" style="margin-right: 0.5em;"/>** 14 Things To Do After Installing Ubuntu 14.04</A><a name="** 14 Things To Do After Installing Ubuntu 14.04" href="#** 14 Things To Do After Installing Ubuntu 14.04" style="margin-left: 0.5em;">¶</a> |
|
1769 |
<DD>page's self-description: Confused what to do after Installing Ubuntu 14.04? Here are some essential things to do after installing Ubuntu 14.04 Trusty Tahr. |
|
1770 | 1791 |
<DT><A HREF="http://www.howtogeek.com/75705/access-shared-folders-in-a-virtualbox-ubuntu-11.04-virtual-machine/" name="http://www.howtogeek.com/75705/access-shared-folders-in-a-virtualbox-ubuntu-11.04-virtual-machine/" ADD_DATE="1365498064" ICON_URI="http://cdn.howtogeek.com/public/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://cdn.howtogeek.com/public/favicon.ico" style="margin-right: 0.5em;"/>Access Shared Folders in a VirtualBox Ubuntu 11.04 Virtual Machine</A><a name="Access Shared Folders in a VirtualBox Ubuntu 11.04 Virtual Machine" href="#Access Shared Folders in a VirtualBox Ubuntu 11.04 Virtual Machine" style="margin-left: 0.5em;">¶</a> |
1771 | 1792 |
<DD>page's self-description: Have you installed Ubuntu 11.04 as a virtual machine in VirtualBox but have had problems getting the Shared Folders feature to work? We were able to add a shared folder, but were unable to access it. |
1793 |
<DT><A HREF="ftp://ftp.ucsb.edu/pub/mirrors/linux/ubuntu/" name="ftp://ftp.ucsb.edu/pub/mirrors/linux/ubuntu/" ADD_DATE="1398288887" ICON_URI="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8%2F9hAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAeBJREFUeNqcU81O20AQ%2FtZ2AgQSYQRqL1UPVG2hAUQkxLEStz4DrXpLpD5Drz31Cajax%2Bghhx6qHIJURBTxIwQRwopCBbZjHMcOTrzermPipsSt1Iw03p3ZmW%2B%2B2R0TxhgOD34wjCHZlQ0iDYz9yvEfhxMTCYhEQDIZhkxKd2sqzX2TOD2vBQCQhpPefng1ZP2dVPlLLdpL8SEMcxng%2Fbs0RIHhtgs4twxOh%2BHjZxvzDx%2F3GQQiDFISiRBLFMPKTRMollzcWECrDVhtxtdRVsL9youPxGj%2FbdfFlUZhtDyYbYqWRUdai1oQRZ5oHeHl2gNM%2B01Uqio8RlH%2BnsazJzNwXcq1B%2BiXPHprlEEymeBfXs1w8XxxihfyuXqoHqpoGjZM04bddgG%2F9%2B8WGj87qDdsrK9m%2BoA%2BpbhQTDh2l1%2Bi2weNbSHMZyjvNXmVbqh9Fj5Oz27uEoP%2BSTxANruJs9L%2FT6P0ewqPx5nmiAG5f6AoCtN1PbJzuRyJAyDBzzSQYvErf06yYxhGXlEa8H2KVGoasjwLx3Ewk858opQWXm%2B%2Fib9EQrBzclLLLy89xYvlpchvtixcX6uo1y%2FzsiwHrkIsgKbp%2BYWFOWicuqppoNTnStHzPFCPQhBEBOyGAX4JMADFetubi4BSYAAAAABJRU5ErkJggg%3D%3D" LAST_CHARSET="windows-1252"><img width="16" height="16" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8%2F9hAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAeBJREFUeNqcU81O20AQ%2FtZ2AgQSYQRqL1UPVG2hAUQkxLEStz4DrXpLpD5Drz31Cajax%2Bghhx6qHIJURBTxIwQRwopCBbZjHMcOTrzermPipsSt1Iw03p3ZmW%2B%2B2R0TxhgOD34wjCHZlQ0iDYz9yvEfhxMTCYhEQDIZhkxKd2sqzX2TOD2vBQCQhpPefng1ZP2dVPlLLdpL8SEMcxng%2Fbs0RIHhtgs4twxOh%2BHjZxvzDx%2F3GQQiDFISiRBLFMPKTRMollzcWECrDVhtxtdRVsL9youPxGj%2FbdfFlUZhtDyYbYqWRUdai1oQRZ5oHeHl2gNM%2B01Uqio8RlH%2BnsazJzNwXcq1B%2BiXPHprlEEymeBfXs1w8XxxihfyuXqoHqpoGjZM04bddgG%2F9%2B8WGj87qDdsrK9m%2BoA%2BpbhQTDh2l1%2Bi2weNbSHMZyjvNXmVbqh9Fj5Oz27uEoP%2BSTxANruJs9L%2FT6P0ewqPx5nmiAG5f6AoCtN1PbJzuRyJAyDBzzSQYvErf06yYxhGXlEa8H2KVGoasjwLx3Ewk858opQWXm%2B%2Fib9EQrBzclLLLy89xYvlpchvtixcX6uo1y%2FzsiwHrkIsgKbp%2BYWFOWicuqppoNTnStHzPFCPQhBEBOyGAX4JMADFetubi4BSYAAAAABJRU5ErkJggg%3D%3D" style="margin-right: 0.5em;"/>Index of ftp://ftp.ucsb.edu/pub/mirrors/linux/ubuntu/</A><a name="Index of ftp://ftp.ucsb.edu/pub/mirrors/linux/ubuntu/" href="#Index of ftp://ftp.ucsb.edu/pub/mirrors/linux/ubuntu/" style="margin-left: 0.5em;">¶</a> |
|
1772 | 1794 |
<DT><A HREF="https://help.ubuntu.com/community/KVM/VirtManager" name="https://help.ubuntu.com/community/KVM/VirtManager" ADD_DATE="1367519739" ICON_URI="https://help.ubuntu.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://help.ubuntu.com/favicon.ico" style="margin-right: 0.5em;"/>KVM/VirtManager - Community Ubuntu Documentation</A><a name="KVM/VirtManager - Community Ubuntu Documentation" href="#KVM/VirtManager - Community Ubuntu Documentation" style="margin-left: 0.5em;">¶</a> |
1773 | 1795 |
</DL><p> |
1774 | 1796 |
<DT><A HREF="http://sourcecodebrowser.com/liblockfile/1.08/lockfile_8h.html#a07dd899d02573b6d2634a27ac2f23204" name="http://sourcecodebrowser.com/liblockfile/1.08/lockfile_8h.html#a07dd899d02573b6d2634a27ac2f23204" ADD_DATE="1359846610" LAST_CHARSET="UTF-8"><img width="16" height="16" src="blank.gif" style="margin-right: 0.5em;"/>liblockfile 1.08, lockfile_8h.html</A><a name="liblockfile 1.08, lockfile_8h.html" href="#liblockfile 1.08, lockfile_8h.html" style="margin-left: 0.5em;">¶</a> |
... | ... | |
2234 | 2256 |
|
2235 | 2257 |
did the trick. |
2236 | 2258 |
</DL><p> |
2259 |
<DT><A HREF="http://www.serverwatch.com/tutorials/article.php/3937741/Monitor-Progress-with-Pipe-Viewer.htm" name="http://www.serverwatch.com/tutorials/article.php/3937741/Monitor-Progress-with-Pipe-Viewer.htm" ADD_DATE="1398277533" ICON_URI="http://www.serverwatch.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.serverwatch.com/favicon.ico" style="margin-right: 0.5em;"/>* Monitor Progress with Pipe Viewer</A><a name="* Monitor Progress with Pipe Viewer" href="#* Monitor Progress with Pipe Viewer" style="margin-left: 0.5em;">¶</a> |
|
2260 |
<DD>page's self-description: For sys admins, running a process can feel like driving cross-country without a road map. Pipe Viewer is one way to answer the question, 'are we there yet?' |
|
2261 |
|
|
2262 |
"apt-get install pv" |
|
2263 |
|
|
2264 |
"pv -p -s ${SIZE}k" |
|
2237 | 2265 |
<DT><A HREF="http://stackoverflow.com/questions/626533/how-can-i-ssh-directly-to-a-particular-directory#comment23522529_626574" name="http://stackoverflow.com/questions/626533/how-can-i-ssh-directly-to-a-particular-directory#comment23522529_626574" ADD_DATE="1393227467" ICON_URI="http://cdn.sstatic.net/stackoverflow/img/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://cdn.sstatic.net/stackoverflow/img/favicon.ico" style="margin-right: 0.5em;"/>** bash - How can I ssh directly to a particular directory? - Stack Overflow</A><a name="** bash - How can I ssh directly to a particular directory? - Stack Overflow" href="#** bash - How can I ssh directly to a particular directory? - Stack Overflow" style="margin-left: 0.5em;">¶</a> |
2238 | 2266 |
<DD>" |
2239 | 2267 |
$ ssh -t xxx.xxx.xxx.xxx "cd /directory_wanted && exec \$SHELL" |
Also available in: Unified diff
web/links/index.htm: updated to Firefox bookmarks: Ubuntu: Ubuntu 14.04 upgrade: added things broken by it. PostgreSQL: fixed links.