text:
You are currently browsing the tag archive for the 'planning' tag.
The Center for Digital Education published its annual report:
Technology Innovation in Education
From the compelling data and case studies in the report, five main points emerge:
- The recession has gravely impacted K-12 and Higher Education technology investment.
- Technology use among students and educators is growing and diversifying; especially mobile devices.
- Strategic planning, particularly respecting infrastructure and standards, is necessary to effective educational technology use in the future.
- Training and support, especially for educators, are essential to effective educational technology use in the future.
- Models of effective practice for planning, investment, and training already exist in our schools. Capable leadership involves making use of those models and the people on the ground who are driving them.
The report sums with this conclusion;
"When proper technology professional development is in place; teachers are able to better deliver a lesson, students are more informed digital citizens and administrators effectively implement technology that is aligned with learning objectives and standards." P.13.
I put it thus: Staff development will get you through times of no money better than money will get you through times of no staff development.

subset: commoncrawl


text:
Difference between revisions of "TodoDone90"
From PostgreSQL wiki
(Create 9.0 done TODO list)
(No difference)
Revision as of 00:43, 10 August 2010
- 1 Administration
- 2 Data Types
- 3 Functions
- 4 Multi-Language Support
- 5 Views / Rules
- 6 SQL Commands
- 7 Integrity Constraints
- 8 Server-Side Languages
- 9 Clients
- 10 Triggers
- 11 Inheritance
- 12 Indexes
- 13 Catalogs
- 14 Sorting
- 15 Fsync
- 16 Cache Usage
- 17 Vacuum
- 18 Locking
- 19 Startup Time Improvements
- 20 Write-Ahead Log
- 21 Optimizer / Executor
- 22 Background Writer
- 23 Concurrent Use of Resources
- 25 Miscellaneous Performance
- 26 Miscellaneous Other
- 27 Source Code
- 28 Exotic Features
- 29 Features We Do Not Want
This list contains all known PostgreSQL bugs and feature requests. If you would like to work on an item, please read the Developer FAQ first. There is also a development information page.
- - marks ordinary, incomplete items
- [E] - marks items that are easier to implement
- [D] - marks changes that are done, and will appear in the next major release
For help on editing this list, please see Talk:Todo. Please do not add items here without discussion on the mailing list.
- Allow administrators to cancel multi-statement idle transactions
- This allows locks to be released, but it is complex to report the cancellation back to the client.
- Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly
- Set proper permissions on non-system schemas during db creation
- Currently all schemas are owned by the super-user because they are copied from the template1 database. However, since all objects are inherited from the template database, it is not clear that setting schemas to the db owner is correct.
- Allow log_min_messages to be specified on a per-module basis
- This would allow administrators to see more detailed information from specific sections of the backend, e.g. checkpoints, autovacuum, etc. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. See also Logging Brainstorm.
- Simplify ability to create partitioned tables
- This would allow creation of partitioned tables without requiring creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection. Options could include range and hash partition selection. See also Table partitioning
- Allow auto-selection of partitioned tables for min/max() operations
- There was a patch on -hackers from July 2009, but it has not been merged: MIN/MAX optimization for partitioned table
- [D] Allow more complex user/database default GUC settings
- Currently ALTER USER and ALTER DATABASE support per-user and per-database defaults. Consider adding per-user-and-database defaults so things like search_path can be defaulted for a specific user connecting to a specific database.
- Allow custom variables to appear in pg_settings()
- Have custom variables be transaction safe
- [D] Allow custom variables to be created only by super-users but modified by ordinary uses, where appropriate
- Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles
- Improve server security options
- Prevent query cancel packets from being replayed by an attacker, especially when using SSL
- Provide a way to query the log collector subprocess to determine what the currently active log file is
- Allow the client to authenticate the server in a Unix-domain socket connection, e.g., using SO_PEERCRED
- [D] Allow the client to set an application_name to appear in pg_stat_activity
- [D] Allow server-side enforcement of password policies
- Password checks might include password complexity or non-reuse of passwords. This facility will require the client to send password creation/changes to the server in plain-text, not MD5.
- Allow custom daemons to be automatically stopped/started along postmaster
- This allows easier administration of daemons like user job schedulers or replication-related daemons.
Configuration files
- Allow pg_hba.conf to specify host names along with IP addresses
- Host name lookup could occur when the postmaster reads the pg_hba.conf file, or when the backend starts. Another solution would be to reverse lookup the connection IP and check that hostname against the host names in pg_hba.conf. We could also then check that the host name maps to the IP address.
- Consider normalizing fractions in postgresql.conf, perhaps using '%'
- Allow Kerberos to disable stripping of realms so we can check the username@realm against multiple realms
- Improve LDAP authentication configuration options
- Add external tool to auto-tune some postgresql.conf parameters
- Add 'hostgss' pg_hba.conf option to allow GSS link-level encryption
- Process pg_hba.conf keywords as case-insensitive
- Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2
- Currently all objects in the default database tablespace must have default tablespace specifications. This is because new databases are created by copying directories. If you mix default tablespace tables and tablespace-specified tables in the same directory, creating a new database from such a mixed directory would create a new database with tables that had incorrect explicit tablespaces. To fix this would require modifying pg_class in the newly copied database, which we don't currently do.
- Allow reporting of which objects are in which tablespaces
- This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that returns the databases which use a specific tablespace, so this requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.
- Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original
- [D] Allow per-tablespace random_page_cost
Statistics Collector
- Allow statistics last vacuum/analyze execution times to be displayed without requiring track_counts to be enabled
- Clear table counters on TRUNCATE
- Allow the clearing of cluster-level statistics
Point-In-Time Recovery (PITR)
- [D] Allow a warm standby system to also allow read-only statements
- [E] Create dump tool for write-ahead logs for use in determining transaction id for point-in-time recovery
- This is useful for checking PITR recovery.
- Allow recovery.conf to support the same syntax as postgresql.conf, including quoting
- Allow archive_mode to be changed without server restart?
- Consider avoiding WAL switching via archive_timeout if there has been no database activity
- [E] Expose pg_controldata via SQL interface
- Helpful for monitoring replicated databases; initial patch
- Allow SSL authentication/encryption over unix domain sockets
- Allow SSL key file permission checks to be optionally disabled when sharing SSL keys with other applications
- Allow SSL CRL files to be re-read during configuration file reload, rather than requiring a server restart
- Unlike SSL CRT files, CRL (Certificate Revocation List) files are updated frequently
- Allow automatic selection of SSL client certificates from a certificate store
- Send full certificate server chain to client
Standby server mode
- Allow pg_xlogfile_name() to be used in recovery mode
- [D] Redefine smart shutdown in standby mode to exist as soon as all read-only connections are gone.
- Fix things so that any such variables inherited from the server environment are intentionally *NOT* used for making SR connections.
- [D] Consider changing the calculation of superused_reserved_connections so that replication connections don't consume superuser_reserved_connections slots.
- Add a new privilege for connecting for streaming replication
- Add capability to take and send a base backup over the streaming replication connection, making it possible to initialize a new standby server from a running primary server without a WAL archive or other access to the primary server.
Data Types
- Reduce storage space for small NUMERICs
- Add support for public SYNONYMs
- Add support for SQL-standard GENERATED/IDENTITY columns
- Consider placing all sequences in a single table, or create a system view
- Consider a special data type for regular expressions
- Reduce BIT data type overhead using short varlena headers
- Allow adding/renaming/removing enumerated values to an existing enumerated data type
- Support scoped IPv6 addresses in inet type
- Add JSON (JavaScript Object Notation) data type
- This would behave similar to the XML data type, which is stored as text, but allows element lookup and conversion functions.
- Considering improving performance of computing CHAR() value lengths
- Fix CREATE CAST on DOMAINs
- Allow domains to be cast
- Make domains work better with polymorphic functions
Dates and Times
- Allow TIMESTAMP WITH TIME ZONE to store the original timezone information, either zone name or offset from UTC
- If the TIMESTAMP value is stored with a time zone name, interval computations should adjust based on the time zone rules.
- Have timestamp subtraction not call justify_hours()?
- Improve timestamptz subtraction to be DST-aware
- Currently subtracting one date from another that crosses a daylight savings time adjustment can return '1 day 1 hour', but adding that back to the first date returns a time one hour in the future. This is caused by the adjustment of '25 hours' to '1 day 1 hour', and '1 day' is the same time the next day, even if daylight savings adjustments are involved.
- [D] Revise the src/timezone/tznames abbreviation files:
- to add missing abbreviations
- to find abbreviations that can be safely promoted to the Default list
- BUG #4377: casting result of timeofday() to timestamp fails in some timezones
- Add function to allow the creation of timestamps using parameters
- Add support for arrays of domains
- Add function to detect if an array is empty
- Improve handling of empty arrays
- Improve handling of NULLs in arrays
Binary Data
- Allow read/write into TOAST values like large objects
- This requires the TOAST column to be stored EXTERNAL.
- Add API for 64-bit large object access
MONEY Data Type
- Add locale-aware MONEY type, and support multiple currencies
- MONEY dumps in a locale-specific format making it difficult to restore to a system with a different locale
Text Search
- Allow dictionaries to change the token that is passed on to later dictionaries
- Consider a function-based API for '@@' searches
- Improve text search error messages
- Consider changing error to warning for strings larger than one megabyte
- tsearch and tsdicts regression tests fail in Turkish locale on glibc
- tsquery negator operator treated as part of lexeme
- Allow xml arrays to be cast to other data types
- Make it work reliably for non-UTF8 server encoding (xpath()) in particular is known to not work)
- [D] Inline ORDER BY for XMLAGG. Example: "... XMLAGG(XMLELEMENT(...) ORDER BY col1) ..." (should be made to work with all aggregate functions)
- XML Canonical: Convert XML documents to canonical form to compare them. libxml2 has support for this.
- Pretty-printing XML: Parse a document and serialize it back in some indented form. libxml2 might support this.
- In some cases shredding could be better option (if there is no need in keeping XML docs entirely; if we have already developed tools that understand only relational data; etc) -- it would be a separate module that implements annotated schema decomposition technique, similar to DB2 and SQL Server functionality.
- xpath_table needs to be implemented/implementable to get rid of contrib/xml2 [9]
- xpath_table is pretty broken anyway [10]
- xpath_exists() is needed. It checks, whether or not the path specified exists in the XML value. (W/o this function we need to use weird "array_dims(xpath(...)) IS NOT NULL" syntax.)
- better handling of PIs and DTDs in xmlconcat() [13]
- Add INET overlaps operator, for use by exclusion constraints
- Add missing parameter handling in to_char()
- Throw an error from to_char() instead of printing a string of "#" when a number doesn't fit in the desired output format.
- discussed in "to_char, support for EEEE format"
- [D] Add functions to get/set bit values
- Allow to_char() on interval values to accumulate the highest unit requested
Some special format flag would be required to request such accumulation. Such functionality could also be added to EXTRACT. Prevent accumulation that crosses the month/day boundary because of the uneven number of days in a month.
- to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65
- to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
- to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
- to_char(INTERVAL '3 years 5 months','MM') => 41
- Allow SQL-language functions to reference parameters by parameter name
- Currently SQL-language functions can only refer to dollar parameters, e.g. $1
- Enforce typmod for function inputs, function results and parameters for spi_prepare'd statements called from PLs
- Tighten function permission checks
- Fix IS OF so it matches the ISO specification, and add documentation
- [D] Add missing operators for geometric data types
- Some geometric types do not have the full suite of geometric operators, e.g. box @> point
- Add overlaps geometric operators that ignore point overlaps
- Implement Boyer-Moore searching in LIKE queries
- Prevent malicious functions from being executed with the permissions of unsuspecting users
- Index functions are safe, so VACUUM and ANALYZE are safe too. Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
- Reduce memory usage of aggregates in set returning functions
- Fix /contrib/ltree operator
- Fix inconsistent precedence of =, >, and < compared to <>, >=, and <=
- Fix regular expression bug when using complex back-references
- Have /contrib/dblink reuse unnamed connections
- Allow calling of a procedure outside a SELECT that can control the transaction state
- [D] Add has_sequence_privilege()
- Improve formatting of pg_get_viewdef() output
- Add printf()-like functionality
- Fix to_number() handling for values not matching the format string
- Add function to dump pg_depend information cleanly
Multi-Language Support
- Allow more fine-grained collation selection; add CREATE COLLATION.
Right now the collation is fixed at database creation time.
- Re: Patch for collation using ICU
- FW: Win32 unicode vs ICU
- Re: FW: Win32 unicode vs ICU
- Proof of concept COLLATE support with patch
- For review: Initial support for COLLATE
- Proposed COLLATE implementation
- TODO item: locale per database patch (new iteration)
- Re: FW: Win32 unicode vs ICU
- Re: Fixed length data types issue
- [WIP] collation support revisited (phase 1)
- Todo:Collate
- Todo:ICU
- WIP patch: Collation support
- Re: WIP patch: Collation support
- PGDay.it collation discussion notes
- Unicode collation algorithm
- Add a LOCALE option to CREATE DATABASE, as a shorthand
- Add URL to more complete multi-byte regression tests
- Fix contrib/fuzzystrmatch to work with multibyte encodings
- Set client encoding based on the client operating system encoding
- Currently client_encoding is set in postgresql.conf, which defaults to the server encoding.
- Change memory allocation for multi-byte functions so memory is allocated inside conversion functions
- Currently we preallocate memory based on worst-case usage.
- Add ability to use case-insensitive regular expressions on multi-byte characters
- ILIKE already works with multi-byte characters
- Improve encoding of connection startup messages sent to the client
- Currently some authentication error messages are sent in the server encoding
- Have pg_stat_activity display query strings in the correct client encoding
- More sensible support for Unicode combining characters, normal forms
Views / Rules
- Automatically create rules on views so they are updateable, per SQL:2008
- We can only auto-create rules for simple views. For more complex cases users will still have to write rules manually.
- Allow VIEW/RULE recompilation when the underlying tables change
- This is both difficult and controversial.
- Make it possible to use RETURNING together with conditional DO INSTEAD rules, such as for partitioning setups
- Add the ability to automatically create materialized views
- Right now materialized views require the user to create triggers on the main table to keep the summary table current. SQL syntax should be able to manage the triggers and summary table automatically. A more sophisticated implementation would automatically retrieve from the summary table when the main table is referenced, if possible. See Materialized Views for implementation details
- Improve ability to modify views via ALTER TABLE
- Prevent low-cost functions from seeing unauthorized view rows
SQL Commands
- Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
- [E] Fix TRUNCATE ... RESTART IDENTITY so its effect on sequences is rolled back on transaction abort
- Allow finer control over the caching of prepared query plans
- Currently anonymous (un-named) queries prepared via the wire protocol are replanned every time bind parameters are supplied --- allow SQL PREPARE to do the same. Also, allow control over replanning prepared queries either manually or automatically when statistics for execute parameters differ dramatically from those used during planning.
- Improve logging of prepared transactions recovered during startup
- Allow prepared transactions with temporary tables created and dropped in the same transaction, and when an ON COMMIT DELETE ROWS temporary table is accessed
- Add SQL-standard MERGE/REPLACE/UPSERT command
- MERGE is typically used to merge two tables. REPLACE or UPSERT command does UPDATE, or on failure, INSERT. See SQL MERGE for notes on the implementation details.
- [D] Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
- Enable standard_conforming_strings by default in 9.1?
- When this is done, backslash-quote should be prohibited in non-E'' strings because of possible confusion over how such strings treat backslashes. Basically, '' is always safe for a literal single quote, while \' might or might not be based on the backslash handling rules.
- Allow the count returned by SELECT, etc to be represented as an int64 to allow a higher range of values
- Add support for WITH RECURSIVE ... CYCLE
- Add DEFAULT .. AS OWNER so permission checks are done as the table owner
- This would be useful for SERIAL nextval() calls and CHECK constraints.
- Add column to pg_stat_activity that shows the progress of long-running commands like CREATE INDEX and VACUUM
- Allow INSERT/UPDATE/DELETE ... RETURNING inside a SELECT 'FROM' clause or target list
- Actually it would be saner to allow this in WITH
- Allow INSERT/UPDATE/DELETE ... RETURNING in common table expressions
- Add comments on system tables/columns using the information in catalogs.sgml
- Ideally the information would be pulled from the SGML file automatically.
- Prevent the specification of conflicting transaction read/write options
- Support LATERAL subqueries
- Lateral subqueries can reference columns of tables defined outside the subquery at the same level, i.e. laterally. For example, a LATERAL subquery in a FROM clause could reference tables defined in the same FROM clause. Currently only the columns of tables defined above subqueries are recognized.
- [D] Forbid COMMENT on columns of an index
- Postgres currently allows comments to be placed on the columns of an index, but pg_dump doesn't handle them and the column names themselves are implementation-dependent.
- Add support for functional dependencies
- This would allow omitting GROUP BY columns when grouping by the primary key.
- Optimize ON COMMIT DELETE ROWS
- Currently deletions are excessively performed
- Have WITH CONSTRAINTS also create constraint indexes
- Move NOT NULL constraint information to pg_constraint
- Currently NOT NULL constraints are stored in pg_attribute without any designation of their origins, e.g. primary keys. One manifest problem is that dropping a PRIMARY KEY constraint does not remove the NOT NULL constraint designation. Another issue is that we should probably force NOT NULL to be propagated from parent tables to children, just as CHECK constraints are. (But then does dropping PRIMARY KEY affect children?)
- Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message
- Allow CREATE TABLE to optionally create a table if it does not already exist, without throwing an error
- The fact that tables contain data makes this more complex than other CREATE OR REPLACE operations.
- [D] Have CREATE TABLE LIKE copy column storage parameters
- CREATE OR REPLACE FUNCTION might leave dependent objects depending on the function in inconsistent state
- Allow temporary tables to exist as empty by default in all sessions
- [D] Add OR REPLACE to CREATE LANGUAGE
- Allow the creation of "distinct" types
- Consider analyzing temporary tables when they are first used in a query
- Autovacuum cannot analyze or vacuum temporary tables.
- Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
- Research self-referential UPDATEs that see inconsistent row versions in read-committed mode
- Improve performance of EvalPlanQual mechanism that rechecks already-updated rows
- This is related to the previous item, which questions whether it even has the right semantics
- Have ALTER TABLE RENAME rename SERIAL sequence names
- [E] Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
- Have ALTER SEQUENCE RENAME rename the sequence name stored in the sequence table
- Allow moving system tables to other tablespaces, where possible
- Currently non-global system tables must be in the default database tablespace. Global system tables can never be moved.
- Allow column display reordering by recording a display, storage, and permanent id for every column?
- Allow an existing index to be marked as a table's primary key
- Allow ALTER TYPE on composite types to perform operations similar to ALTER TABLE
- Don't require table rewrite on ALTER TABLE ... ALTER COLUMN TYPE, when the old and new data types are binary compatible
- Automatically maintain clustering on a table
- This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only partially filled for easier reorganization. Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too. A third idea would be to store heap rows in hashed groups, perhaps using a user-supplied hash function.
- [E] Add default clustering to system tables
- To do this, determine the ideal cluster index for each system table and set the cluster setting during initdb.
- Improve CLUSTER performance by sorting to reduce random I/O
- Allow COPY to report error lines and continue
- This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure.
- Allow COPY on a newly-created table to skip WAL logging
- On crash recovery, the table involved in the COPY would be removed or have its heap and index files truncated. One issue is that no other backend should be able to add to the table at the same time, which is something that is currently allowed. This currently is done if the table is created inside the same transaction block as the COPY because no other backends can see the table.
- Allow COPY FROM to create index entries in bulk
- Allow COPY in CSV mode to control whether a quoted zero-length string is treated as NULL
- Currently this is always treated as a zero-length string, which generates an error when loading into an integer column
- Improve COPY performance
- Allow COPY to report errors sooner
- [D] Improve bytea COPY format
- Allow COPY to handle other number formats eg. the German notation. Best would be something like WITH DECIMAL ','.
- Allow a stalled COPY to exit if the backend is terminated
- [D] Allow GRANT/REVOKE permissions to be applied to all schema objects with one command
- The proposed syntax is: GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW TABLES IN public TO phpuser;
- [D] Allow GRANT/REVOKE permissions to be inherited by objects based on schema permissions
- Allow dropping of a role that has connection rights
- Provide some guarantees about the behavior of cursors that invoke volatile functions
- Rationalize the discrepancy between settings that use values in bytes and SHOW that returns the object count
- [D] Allow LISTEN/NOTIFY to store info in memory rather than tables
- Currently LISTEN/NOTIFY information is stored in pg_listener. Storing such information in memory would improve performance.
- [D] Add optional textual message to NOTIFY
- This would allow an informational message to be added to the notify message, perhaps indicating the row modified or other custom information.
Window Functions
See TODO items for window functions.
- Support creation of user-defined window functions.
- We have the ability to create new window functions written in C. Is it worth the effort to create an API that would let them be written in PL/pgsql, etc?
- Implement full support for window framing clauses.
In addition to done clauses described in the latest doc, these clauses are not implemented yet.
- Look at tuplestore performance issues.
- The tuplestore_in_memory() thing is just a band-aid, we ought to try to solve it properly. tuplestore_advance seems like a weak spot as well.
- Teach planner to evaluate multiple windows in the optimal order.
- Currently windows are always evaluated in the query-specified order.
Integrity Constraints
- [D] Allow DEFERRABLE UNIQUE constraints
- This would allow UPDATE tab SET col = col + 1 to work if col has a unique index. Currently, uniqueness checks are done while the command is being executed, rather than at the end of the statement or transaction.
Referential Integrity
- Fix problem when cascading referential triggers make changes on cascaded tables, seeing the tables in an intermediate state
- Optimize referential integrity checks
Server-Side Languages
- Add more fine-grained specification of functions taking arbitrary data types
- Add support for returning multiple result sets?
- [D] Allow function parameters to be passed by name, get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
- Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname)
- Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables
- Because a row is not scalar, do not allow assignment from NULL-valued scalars.
- [D] Review handling of MOVE and FETCH
- [D] Improve logic of determining if an identifier is a variable or a column name
- Consider keeping separate cached copies when search_path changes
- [D] Improve PL/pgSQL's ability to cope with rowtypes containing dropped columns
- Improve handling of NULL row values vs. NULL rows
- Allow data to be passed in native language formats, rather than only text
- Add tracebacks
- [D] Add support for Python 3
- Create a new restricted execution class that will allow passing function arguments in as locals. Passing them as globals means functions cannot be called recursively.
- Functions cache the input and output functions for their arguments, so the following will make PostgreSQL unhappy: create table users (first_name text, last_name text); create function user_name(user) returns text as 'mycode' language plpython; select user_name(user) from users; alter table add column user_id integer; select user_name(user) from users; You have to drop and create the function(s) each time its arguments are modified (not nice), or don't cache the input and output functions (slower?), or check if the structure of the argument has been altered (is this possible, easy, quick?) and recreate cache.
- Add a function like pg_get_indexdef() that report more detailed index information
- Allow pg_ctl to work properly with configuration files located outside the PGDATA directory
- pg_ctl can not read the pid file because it isn't located in the config directory but in the PGDATA directory. The solution is to allow pg_ctl to read and understand postgresql.conf to find the data_directory value.
- Have the postmaster write a random number to a file on startup that pg_ctl checks against the contents of a pg_ping response on its initial connection (without login)
- This will protect against connecting to an old instance of the postmaster in a different or deleted subdirectory.
- Modify pg_ctl behavior and exit codes to make it easier to write an LSB conforming init script
- It may be desirable to condition some of the changes on a command-line switch, to avoid breaking existing scripts. A Linux shell (sh) script is referenced which has been tested and seems to provide a high degree of conformance in multiple environments. Study of this script might suggest areas where pg_ctl could be modified to make writing an LSB conforming script easier; however, some aspects of that script would be unnecessary with other suggested changes to pg_ctl, and discussion on the lists did not reach consensus on support for all aspects of this script. Further discussion of particular changes is needed before beginning any work.
- Have psql \ds show all sequences and their settings
- Move psql backslash database information into the backend, use mnemonic commands?
- This would allow non-psql clients to pull the same information out of the database as psql.
- Make psql's \d commands more consistent in its handling of schemas
- Add auto-expanded mode so expanded output is used if the row length is wider than the screen width.
- Consider using auto-expanded mode for backslash commands like \df+.
- Prevent tab completion of SET TRANSACTION from querying the database and therefore preventing the transaction isolation level from being set.
- Currently SET <tab> causes a database lookup to check all supported session variables. This query causes problems because setting the transaction isolation level must be the first statement of a transaction.
- Add a \set variable to control whether \s displays line numbers
- Another option is to add \# which lists line numbers, and allows command execution.
- Prevent escape string warnings when object names have backslashes
- Include the symbolic SQLSTATE name in verbose error reports
- Add prompt escape to display the client and server versions
- Add option to wrap column values at whitespace boundaries, rather than chopping them at a fixed width.
- Currently, "wrapped" format chops values into fixed widths. Perhaps the word wrapping could use the same algorithm documented in the W3C specification.
- Add "auto" expanded mode that outputs in expanded format if "wrapped" mode can't wrap the output to the screen width
- Support the ReST table output format
- Details about the ReST format: http://docutils.sourceforge.net/rst.html#reference-documentation
- Add option to print advice for people familiar with other databases
- Consider showing TOAST and index sizes in \dt+
- Allow \dd to show constraint comments
- Add ability to edit views with \ev
- Add \dL to show languages
- [E] Distinguish between unique indexes and unique constraints in \d+
- Fix FETCH_COUNT to handle SELECT ... INTO and WITH queries
- Prevent psql from sending remaining single-line multi-statement queries after reconnecting
pg_dump / pg_restore
- [D] Add dumping of comments on composite type columns
- [E] Add full object name to the tag field. eg. for operators we need '=(integer, integer)', instead of just '='.
- Avoid using platform-dependent locale names in pg_dumpall output
- Using native locale names puts roadblocks in the way of porting a dump to another platform. One possible solution is to get CREATE DATABASE to accept some agreed-on set of locale names and fix them up to meet the platform's requirements.
- Add support for multiple pg_restore -t options, like pg_dump
- pg_restore's -t switch is less useful than pg_dump's in quite a few ways: no multiple switches, no pattern matching, no ability to pick up indexes and other dependent items for a selected table. It should be made to handle this switch just like pg_dump does.
- Allow pg_dump --clean to drop roles that own objects or have privileges
- tgl says: if this is about pg_dumpall, it's done as of 8.4. If it's really about pg_dump, what does it mean? pg_dump has no business dropping roles.
- Allow pg_dump to utilize multiple CPUs and I/O channels by dumping multiple objects simultaneously
- The difficulty with this is getting multiple dump processes to produce a single dump output file. It also would require several sessions to share the same snapshot.
- Remove support for dumping from pre-7.3 servers
- In 7.3 and later, we can get accurate dependency information from the server. pg_dump still contains a lot of crufty code to try to deal with the lack of dependency info in older servers, but the usefulness of maintaining that code grows small.
- Allow pre/data/post files when schema and data are dumped separately, for performance reasons
- Refactor handling of database attributes between pg_dump and pg_dumpall
- Currently only pg_dumpall emits database attributes, such as ALTER DATABASE SET commands and database-level GRANTs. Many people wish that pg_dump would do that. One proposal is to let pg_dump issue such commands if the -C switch was used, but it's unclear whether that will satisfy the demand.
- Change pg_dump so that a comment on the dumped database is applied to the loaded database, even if the database has a different name.
- This will require new backend syntax, perhaps COMMENT ON CURRENT DATABASE. This is related to the previous item.
- Allow parallel restore of tar dumps
- Docs
- Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.
- [D] Implement SQLDA
- add sqlda support to ecpg in both native and compatibility mode
- Provide a way to specify size of a bytea parameter
- [E] Fix small memory leaks in ecpg
- Memory leaks in a short running application like ecpg are not really a problem, but make debugging more complicated
- Allow re-usage of cursor name variables
- Prevent PQfnumber() from lowercasing unquoted column names
- PQfnumber() should never have been doing lowercasing, but historically it has so we need a way to prevent it
- Allow statement results to be automatically batched to the client
- Currently all statement results are transferred to the libpq client before libpq makes the results available to the application. This feature would allow the application to make use of the first result rows while the rest are transferred, or held on the server waiting for them to be requested by libpq. One complexity is that a statement like SELECT 1/col could error out mid-way through the result set.
- Consider disallowing multiple queries in PQexec() as an additional barrier to SQL injection attacks
- Add PQexecf() that allows complex parameter substitution
- Add SQLSTATE and severity to errors generated within libpq itself
- Add code to detect client encoding and locale from the operating system environment
- [D] Add keepalive support to libpq
- Add support for interface/ipaddress binding to libpq
- Improve storage of deferred trigger queue
- Right now all deferred trigger information is stored in backend memory. This could exhaust memory for very large trigger queues. This item involves dumping large queues into files, or doing some kind of join to process all the triggers, some bulk operation, or a bitmap.
- Allow triggers to be disabled in only the current session.
- This is currently possible by starting a multi-statement transaction, modifying the system tables, performing the desired SQL, restoring the system tables, and committing the transaction. ALTER TABLE ... TRIGGER requires a table lock so it is not ideal for this usage.
- With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
- If the dump is known to be valid, allow foreign keys to be added without revalidating the data.
- When statement-level triggers are defined on a parent table, have them fire only on the parent table, and fire child table triggers only where appropriate
- [D] Support triggers on columns
- Allow AFTER triggers on system tables
- System tables are modified in many places in the backend without going through the executor and therefore not causing triggers to fire. To complete this item, the functions that modify system tables will have to fire triggers.
- Tighten trigger permission checks
- Allow BEFORE INSERT triggers on views
- Add database and transaction-level triggers
- Reduce locking requirements for creating a trigger
- Allow inherited tables to inherit indexes, UNIQUE constraints, and primary/foreign keys
- Honor UNIQUE INDEX on base column in INSERTs/UPDATEs on inherited table, e.g. INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail
- The main difficulty with this item is the problem of creating an index that can span multiple tables.
- Determine whether ALTER TABLE / SET SCHEMA should work on inheritance hierarchies (and thus support ONLY). If yes, implement it.
- ALTER TABLE variants sometimes support recursion and sometimes not, but this is poorly/not documented, and the ONLY marker would then be silently ignored. Clarify the documentation, and reject ONLY if it is not supported.
- Prevent index uniqueness checks when UPDATE does not modify the column
- Uniqueness (index) checks are done when updating a column even if the column is not modified by the UPDATE. However, HOT already short-circuits this in common cases, so more work might not be helpful.
- Allow the creation of on-disk bitmap indexes which can be quickly combined with other bitmap indexes
Such indexes could be more compact if there are only a few distinct values. Such indexes can also be compressed. Keeping such indexes updated can be costly.
- Re: Bitmap index AM
- Bitmap index thoughts
- Stream bitmaps
- Re: Bitmapscan changes - Requesting further feedback
- Updated bitmap index patch
- Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch)
- Bitmap Indexes: request for feedback
- http://email@example.com
- Allow accurate statistics to be collected on indexes with more than one column or expression indexes, perhaps using per-index statistics
- Consider smaller indexes that record a range of values per heap page, rather than having one index entry for every heap row
- This is useful if the heap is clustered by the indexed values.
- Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
- This is difficult because you must upgrade to an exclusive table lock to replace the existing index file. CREATE INDEX CONCURRENTLY does not have this complication. This would allow index compaction without downtime.
- Allow multiple indexes to be created concurrently, ideally via a single heap scan
- pg_restore allows parallel index builds, but it is done via subprocesses, and there is no SQL interface for this.
- Consider sorting entries before inserting into btree index
- Allow index scans to return matching index keys, not just the matching heap locations
- Allow creation of an index that can do comparisons to test if a value is between two column values
- Consider using "effective_io_concurrency" for index scans
- Currently only bitmap scans use this, which might be fine because most multi-row index scans use bitmap scans.
- Fix performance issues in contrib/seg and contrib/cube GiST support
- Support empty indexed values (such as zero-element arrays) properly
- Behave correctly for cases where some elements of an indexed value are NULL
- Support queries that require a full scan
- [D] Pack hash index buckets onto disk pages more efficiently
- Currently only one hash bucket can be stored on a page. Ideally several hash buckets could be stored on a single page and greater granularity used for the hash algorithm.
- [D] Improve performance of information_schema views
- [D] Improve information_schema's entries for precision and scale
- Consider whether duplicate keys should be sorted by block/offset
- Consider being smarter about memory and external files used during sorts
- Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
- Ideally this requires a separate test program that can be run at initdb time or optionally later. Consider O_SYNC when O_DIRECT exists.
- Consider sorting writes during checkpoint
Cache Usage
- Speed up COUNT(*)
- We could use a fixed row count and a +/- count to follow MVCC visibility rules, or a single cached value could be used and invalidated if anyone modifies the table. Another idea is to get a count directly from a unique index, but for this to be faster than a sequential scan it must avoid access to the heap to obtain tuple visibility information.
- Provide a way to calculate an "estimated COUNT(*)"
- Perhaps by using the optimizer's cardinality estimates or random sampling.
- Allow data to be pulled directly from indexes
- Currently indexes do not have enough tuple visibility information to allow data to be pulled from the index without also accessing the heap. One way to allow this is to set a bit on index tuples to indicate if a tuple is currently visible to all transactions when the first valid heap lookup happens. This bit would have to be cleared when a heap tuple is expired. Another idea is to maintain a bitmap of heap pages where all rows are visible to all backends, and allow index lookups to reference that bitmap to avoid heap lookups, perhaps the same bitmap we might add someday to determine which heap pages need vacuuming. Frequently accessed bitmaps would have to be stored in shared memory. One 8k page of bitmaps could track 512MB of heap pages. A third idea would be for a heap scan to check if all rows are visible and if so set a per-table flag which can be checked by index scans. Any change to the table would have to clear the flag. To detect changes during the heap scan a counter could be set at the start and checked at the end --- if it is the same, the table has not been modified --- any table change would increment the counter.
- Consider automatic caching of statements at various levels:
- Parsed query tree
- Query execute plan
- Query results
- Consider increasing internal areas (NUM_CLOG_BUFFERS) when shared buffers is increased
- Consider decreasing the amount of memory used by PrivateRefCount
- Consider allowing higher priority queries to have referenced buffer cache pages stay in memory longer
- [D] Improve VACUUM FULL's speed when major data movement is needed
- For large table adjustments during VACUUM FULL, it would be faster to cluster or reindex rather than update the indexes piecemeal as it does now. Also, this behavior tends to bloat the indexes.
- Auto-fill the free space map by scanning the buffer cache or by checking pages written by the background writer
- Consider having single-page pruning update the visibility map
- https://commitfest.postgresql.org/action/patch_view?id=75
- Re: visibility maps and heap_prune
- Improve tracking of total relation tuple counts now that vacuum doesn't always scan the whole heap
- Bias FSM towards returning free space near the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM
- Consider a more compact data representation for dead tuple locations within VACUUM
- Provide more information in order to improve user-side estimates of dead space bloat in relations
- Prevent long-lived temporary tables from causing frozen-xid advancement starvation
- The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can do that.
- Prevent autovacuum from running if an old transaction is still running from the last vacuum
- Have free space allocation bias away from using trailing table pages
- This improves the chances of truncating the table during vacuum
- Have autoanalyze of parent tables occur when child tables are modified
- Fix priority ordering of read and write light-weight locks
- Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts
- Allow UPDATEs on only non-referential integrity columns not to conflict with referential integrity locks
- Improve deadlock detection when a page cleaning lock conflicts with a shared buffer that is pinned
- Detect deadlocks involving LockBufferForCleanup()
- Consider a lock timeout parameter
- Consider improving serialized transaction behavior to avoid anomalies
Startup Time Improvements
- Experiment with multi-threaded backend for backend creation
- This would prevent the overhead associated with process creation. Most operating systems have trivial process creation time compared to database startup overhead, but a few operating systems (Win32, Solaris) might benefit from threading. Also explore the idea of a single session using multiple threads to execute a statement faster.
Write-Ahead Log
- Eliminate need to write full pages to WAL before page modification
- Currently, to protect against partial disk page writes, we write full page images to WAL before they are modified so we can correct any partial page writes during recovery. These pages can also be eliminated from point-in-time archive files.
- When full page writes are off, write CRC to WAL and check file system blocks on recovery
- If CRC check fails during recovery, remember the page in case a later CRC for that page properly matches.
- Write full pages during file system write and not when the page is modified in the buffer cache
- This allows most full page writes to happen in the background writer. It might cause problems for applying WAL on recovery into a partially-written page, but later the full page will be replaced from WAL.
- Reduce WAL traffic so only modified values are written rather than entire rows
- Allow WAL information to recover corrupted pg_controldata
- Find a way to reduce rotational delay when repeatedly writing last WAL page
- Currently fsync of WAL requires the disk platter to perform a full rotation to fsync again. One idea is to write the WAL to different offsets that might reduce the rotational delay.
- Allow WAL logging to be turned off for a table, but the table might be dropped or truncated during crash recovery
- Allow tables to bypass WAL writes and just fsync() dirty pages on commit. This should be implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using non-default logging should not use referential integrity with default-logging tables. A table without dirty buffers during a crash could perhaps avoid the drop/truncate.
- Allow WAL logging to be turned off for a table, but the table would avoid being truncated/dropped
- To do this, only a single writer can modify the table, and writes must happen only on new pages so the new pages can be removed during crash recovery. Readers can continue accessing the table. Such tables probably cannot have indexes. One complexity is the handling of indexes on TOAST tables.
- Speed WAL recovery by allowing more than one page to be prefetched
- This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay.
- Improve WAL concurrency by increasing lock granularity
- Be more aggressive about creating WAL files
- Have resource managers report the duration of their status changes
- Move pgfoundry's xlogdump to /contrib and have it rely more closely on the WAL backend code
- Close deleted WAL files held open in *nix by long-lived read-only backends
Optimizer / Executor
- Consider increasing the default values of from_collapse_limit, join_collapse_limit, and/or geqo_threshold
- Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual row counts differ by a specified percentage
- Have EXPLAIN ANALYZE report rows as floating-point numbers
- Log statements where the optimizer row estimates were dramatically different from the number of rows actually found?
- Improve how ANALYZE computes in-doubt tuples
- Consider compressed annealing to search for query plans
- This might replace GEQO.
- Consider using a hash for joining to a large IN (VALUES ...) list
- Allow single batch hash joins to preserve outer pathkeys
- "lazy" hash tables - look up only the tuples that are actually requested
- Avoid building the same hash table more than once during the same query
- Avoid hashing for distinct and then re-hashing for hash join
- Allow hashing to be used on arrays, if the element type is hashable
- Improve use of expression indexes for ORDER BY
Background Writer
- Consider having the background writer update the transaction status hint bits before writing out the page
- Implementing this requires the background writer to have access to system catalogs and the transaction status log.
- Consider adding buffers the background writer finds reusable to the free list
- Automatically tune bgwriter_delay based on activity rather then using a fixed interval
- Consider whether increasing BM_MAX_USAGE_COUNT improves performance
- Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency
Concurrent Use of Resources
- Do async I/O for faster random read-ahead of data
Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously.
- Asynchronous I/O Support
- Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
- There's random access and then there's random access
- Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access)
- Experiment with multi-threaded backend for better I/O utilization
- This would allow a single query to make use of multiple I/O channels simultaneously. One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table.
- Experiment with multi-threaded backend for better CPU utilization
- This would allow several CPUs to be used for a single query, such as for sorting or query execution.
- SMP scalability improvements
- Allow user configuration of TOAST thresholds
- Reduce unnecessary cases of deTOASTing
- Reduce costs of repeat de-TOASTing of values
Miscellaneous Performance
- Use mmap() rather than SYSV shared memory or to write WAL files?
- This would remove the requirement for SYSV SHM but would introduce portability issues. Anonymous mmap (or mmap to /dev/zero) is required to prevent I/O overhead.
- Consider mmap()'ing files into a backend?
- Doing I/O to large tables would consume a lot of address space or require frequent mapping/unmapping. Extending the file also causes mapping problems that might require mapping only individual pages, leading to thousands of mappings. Another problem is that there is no way to _prevent_ I/O to disk from the dirty shared buffers so changes could hit disk before WAL is written.
- Consider ways of storing rows more compactly on disk:
- Reduce the row header size?
- Consider reducing on-disk varlena length from four bytes to two because a heap row cannot be more than 64k in length
- Consider transaction start/end performance improvements
- Allow configuration of backend priorities via the operating system
- Though backend priorities make priority inversion during lock waits possible, research shows that this is not a huge problem.
- Consider increasing the minimum allowed number of shared buffers
- Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call
- Consider Cartesian joins when both relations are needed to form an indexscan qualification for a third relation
- Consider not storing a NULL bitmap on disk if all the NULLs are trailing
- Sort large UPDATE/DELETEs so it is done in heap order
- Allow one transaction to see tuples using the snapshot of another transaction
- This would assist multiple backends in working together.
- Consider decreasing the I/O caused by updating tuple hint bits
- Avoid the requirement of freezing pages that are infrequently modified
- If all rows on a page are visible, it is possible to set a bit in the visibility map (once the visibility map is 100% reliable) and not need to freeze the page, avoiding a page rewrite
- Avoid reading in b-tree pages when replaying vacuum records in hot standby mode
Miscellaneous Other
- Deal with encoding issues for filenames in the server filesystem
- Deal with encoding issues in the output of localeconv()
- Provide schema name and other fields available from SQL GET DIAGNOSTICS in error reports
- [E] Provide fallback_application_name in contrib/pgbench, oid2name, and dblink.
Source Code
- Add optional CRC checksum to heap and index pages
- One difficulty is how to prevent hint bit changes from affecting the computed CRC checksum.
- Consider a faster CRC32 algorithm
- Improve the module installation experience (/contrib, etc)
- [D] Update Bonjour to work with newer cross-platform SDK
- Allow creation of universal binaries for Darwin
- Consider GnuTLS if OpenSSL license becomes a problem
- Research use of signals and sleep wake ups
- [D] Add automated check for invalid C++ source code constructs
- Allow C++ code to more easily access backend code
- Consider simplifying how memory context resets handle child contexts
- Create three versions of libpgport to simplify client code
- Improve detection of shared memory segments being used by others by checking the SysV shared memory field 'nattch'
- Implement the non-threaded Avahi service discovery protocol
- [D] Allow table and index WITH options to be specified via hooks, for use with plugins like GiST index methods
- Reduce data row alignment requirements on some 64-bit systems
- Restructure TOAST internal storage format for greater flexibility
- [D] Allow setting of system oids during object creation, for use by pg_migrator
- Add regression tests for pg_dump/restore
- Convert single quotes to apostrophes in the PDF documentation
- Provide a manpage for postgresql.conf
- Change the manpage-generating toolchain to use the new XML-based docbook2x tools
- Consider changing documentation format from SGML to XML
- Document support for N' ' national character string literals, if it matches the SQL standard
- Handle large object comments
- This is difficult to do because the large object doesn't exist when --schema-only is loaded.
- Migrate pg_statistic by dumping it out as a flat file, so analyze is not necessary
- pg_class.oid is not preserved so schema.tablename must be used.
- [D] Diagnose problem where shared memory can sometimes not be attached by postmaster children
- Improve signal handling
- Convert MSVC build system to remove most batch files
- Fix MSVC NLS support, like for to_char()
- [D] Fix locale-aware handling (e.g. monetary) for specific server/client encoding combinations
- Find a correct rint() substitute on Windows
- [D] Reduce compiler warnings on 64-bit Windows
- Fix global namespace issues when using multiple terminal server sessions
- Change from the current autoconf/gmake build system to cmake
- Improve consistency of path separator usage
- [D] Allow compilation using MSVC 2008
Wire Protocol Changes
Exotic Features
- Add pre-parsing phase that converts non-ISO syntax to supported syntax
- This could allow SQL written for other databases to run without modification.
- Add features of Oracle-style packages
- A package would be a schema with session-local variables, public/private functions, and initialization functions. It is also possible to implement these capabilities in any schema and not use a separate "packages" syntax at all.
- Consider allowing control of upper/lower case folding of unquoted identifiers
- Add autonomous transactions
- Give query progress indication
- Rethink our type system
Features We Do Not Want
- All backends running as threads in a single process (not wanted)
- This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features. Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years.
- Optimizer hints (not wanted)
- Optimizer hints are used to work around problems in the optimizer and introduce upgrade and maintenance issues. We would rather have the problems reported and fixed. We have discussed a more sophisticated system of per-class cost adjustment instead, but a specification remains to be developed.
- Embedded server (not wanted)
- While PostgreSQL clients runs fine in limited-resource environments, the server requires multiple processes and a stable pool of resources to run reliably and efficiently. Stripping down the PostgreSQL server to run in the same process address space as the client application would add too much complexity and failure cases. Besides, there are several very mature embedded SQL databases already available.
- Obfuscated function source code (not wanted)
- Obfuscating function source code has minimal protective benefits because anyone with super-user access can find a way to view the code. At the same time, it would greatly complicate backups and other administrative tasks. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.
- Indeterminate behavior for the GROUP BY clause (not wanted)
- At least one other database product allows specification of a subset of the result columns which GROUP BY would need to be able to provide predictable results; the server is free to return any value from the group. This is not viewed as a desirable feature.


text:
It's time for another edition of Gelf's excellent Varsity Letters reading series. This month's slate features former Washington Post staffer and veteran boxing writer William Gildea, the author Theresa Runstedtler (who has written about boxing legend Jack Johnson), and GQ's Mark Kirby, who will discuss his forthcoming soccer magazine, Howler. It's tonight at 7:30 at Le Poisson Rouge. Go!
More from Deadspin


text:
Director Thomas Balmes spent 400 days filming his four baby subjects around the globe in the movie "Babies."
Not surprisingly, he captured a lot of adorable baby firsts for the movie appropriately opening on Mother's Days Weekend -- from one ultimate first (a birth) to some first tentative first steps. Each of the four babies featured in the film hails from a different corner of the world.
"I would say 60 to 70 percent of the film is firsts for them," Balmes tells PopcornBiz. "The idea was to show as many first times as possible."
But when asked to see where this comes through the most dramatically, Balmes recalls the scene of the Mongolian baby "Bayar."
"In Mongolia you had the party and they are celebrating Chinese New Year and they are singing these very specific Mongolian songs with the throat," Balmes recalls.
"And you can really see for the first time the head of the Mongolian baby Bayar hearing such a crazy sound and you can see in his wide eyes that he has never heard that before," he recalls.
Of course most moviegoers will double over laughing during the scene when Bayar first discovers the many uses of toilet paper or has to share his bathtub with a thirsty goat.
"Babies" Features Adorable Baby Firsts
Director Thomas Balmes spent 400 days filming his four baby subjects around the globe in the movie "Babies."


text:
(Yet another unselected entry for TOI story contest!)
Doubly Strong
'Are you sure, Rhea?' asks my mother.
'Of course I'm. Survival of the fittest, mother. I'm not going against Darwin. Also I don't want unnecessary scars on my body.'
It's a known fact that we are all born to die. And frankly, I don't understand why it has to be made into such a big deal. If it were not for my mother I would have said that to the bunch of people outside my house, some of them with young kids, shouting slogans, waving placards, literally wanting me to cut one of my beating hearts out. "Save A Life. Donate!" they shout.
For someone who is one in billions, 7.125 billion to be exact, I expect to be treated better. Scientists are still befuddled regarding my condition that gave me two hearts in my mother's womb. But years of research and sticking needles into me have led them nowhere, and they have labelled me as a freak mutation. It's so rare - literally one in all humankind - that they didn't even name the anomaly (as they call it, I will call it awesomeness). I wanted to name the condition myself, something on the lines of Rhea's Heartsawesome but the doctors aren't thrilled with the suggestion. Instead they want to cut one of them out and save a life. Huh?
An IQ of 180, increased concentration, exceptional athleticism and a phenomenal metabolism rate - are just the few boring benefits of an increased blood circulation. Why would I ever give that up?
I am resolute in my decision and I have declared it in no uncertain terms. There ends the topic. I refuse to allow it to spoil my delightful enjoyment of the scrambled eggs in my plate.
From across the breakfast table my father beams an assuring, approving smile. 'I fully agree with you, my little girl! Ignore the clamouring crowd outside our house. I shall send them away discreetly.'
That is my dear father. He has always been my best friend and supporter. I cannot help wishing my mother came out of her old-fashioned concepts and customs.
Mother's ideas of womanhood are pathetically unrealistic and outdated in our modern world. She has very crazy notions about a woman's duties as a wife, mother and all other roles.
I have heard her consoling our servant maid who suffers hell in the hands of a drunkard husband. Mother advises her to be patient and submissive and to hope for his reformation. The wretch, the maid's husband, does not support his family. Actually the rogue beats her up to snatch her hard-earned money to buy liquor. The irresponsible beast deserves to be put behind the bars. The stupid woman lacks the guts to avail her rights for getting legal help and protection from such endless domestic violence.
I simply can't understand why women, whatever their social status is, refuse to become aware of their legal rights and moral powers. Well, it is virtuous to have a sacrificing nature, I agree. But do the persons for whom the sacrifices are made deserve them? It is odious to see women who are devoid of self-respect. How can they prefer to live in squalor enduring all kinds of injustice and brutality and not seek emancipation? But it is heartening to see slow changes in this sordid scenario.
As I finish my hearty breakfast I can plainly see mother is disappointed with my decision. 'What these people are demanding is atrocious!' I reassert.
'They are only appealing to your softness towards suffering humanity, Rhea!' mother gently argued.
'I am tender-hearted, I do want to alleviate the sufferings of underprivileged people. I am charitable enough to donate food, clothes and money which fortunately we have in abundance. But giving away an organ, even if it is extra, is completely a different matter, is it not? Money can be easily earned but not the God's gift of an extra heart! I am going to jealously guard it as my precious treasure! There is no rethinking to be done on it!' I stand my position.
Hearing Sushma honking her scooty's horn for me I start running to the gate after a hasty goodbye to my parents. With me in the pillion seat Sushma carefully weaves through the small crowd gathered in front of our house. We both love our daily morning routine of going to the swimming pool. On the way we usually stop at the book store, visit a friend or do some other errand.
After a few minutes of vigorous swimming we take a break to have a little chat. I know Sushma is curious to know about the commotion in front of our house. She lives in the same street and has been with me in the same school and college. We are thick friends and there are no secrets between us, not even the love affair between me and her brother Suraj who after finishing his higher studies in the United States has come back to help his father in the management of their family's business empire.
After listening to my account of the incident of sick people demanding me to donate my extra heart she pats my hand with empathy, 'It is your personal choice, Rhea! Nobody has the right to pressurise you to do anything against your wish. Don't fret over the miseries of other people unnecessarily.'
'I cannot for a moment think of donating my heart to these people, Sushma! Certainly not! Doctors may be obsessed with saving the lives of their patients. That is their profession. Their concern. Not my calling. Not my mission.'
Not wanting to dwell on the subject we plunge again into the pool and enjoy the activity joyfully like two carefree fish. Life is wonderful. It is a gift to be able to live it to the full.
After reaching home I leisurely go through the regular ritual of of pampering my skin and hair with the proper nourishments. My next programme is browsing. On my way to the computer desk I momentarily stop near the new books bought in the morning. They can wait till the night, I decide. I first check my mail and then jump into my favourite strategy games, word games and sudoku all of which never fail to invigorate my brain.
When I am about to log out I hear mother setting the table for lunch. I enter the dining hall with a healthy appetite inhaling the aroma of the hot, spicy dishes mother specialises in. I give her a bear hug wanting to make up for the disappointment I caused her in the morning.
Father walks in calling cheerfully, 'Hello, my pretty girls! I am famished!' Mother waits on us filling our plates with tasty, wholesome food. Mother's culinary skills are extraordinary. Father and I retire into the hall with a large bowl of ice cream in hand.
Mother's favourite magazine lying on top of others on the small table near the sofa catches my eye. 'Surrogacy flourishes in India' flashes the cover story. 'Ouch! That is another sanctifying service of woman - lending her womb to pompous childless couples bent on bringing forth heirs with their genes!' are my words of exasperation.
'My dear child, often it is not the money but a noble sense of service which motivates the surrogate mothers,' comments my father. 'Noble! My foot! Adoption is nobler, is it not, father?' Father nods his head in affirmative clearly indicating his not being in the mood for debating the topic.
'Well, it is time for my beauty sleep. I must get up early and spruce myself before my tennis match with Suraj in the evening,' I announce and after a light peck on father's cheek I run upstairs to my room.
In the evening Suraj greets me with his usual charming smile, 'Hi, cutey pie! you look gorgeous!' I accept the compliment with a gracious smile.
'What was the racket in front of your house in the morning that I heard of, sweetie?'
'Heart patients have an eye on my extra heart!' I reply with a sigh.
'Why don't you give it to them if they want it, my sweetheart?' he asks winking mischievously.
'I might if it were a hairpin I'm wearing on my head is what they wanted!' I shrug my shoulders in disdain.
'Ah! I think you are scared of the operation theatre and the masked surgeons with scalpel in hand! So, you are chicken-hearted and not double-hearted as everybody thinks!' he teases me. I glare at him angrily.
'Oh! Come on, baby! You are clinging to your toy, you mean kid! No sharing! No caring!' he continues his banter.
I turn my back and begin to walk away. He pulls me back, 'Don't leave me, my little piggie! I shall perish without you!'
'Why do you want a heartless girl, may I know?' I gnash my teeth.
'Heartless? Oh! My darling! You have two hearts, my awesome girl!' he exclaims with eyes wide in awe and adoration.
'You decide one heart is enough for me, you male chauvinist pig?' I hiss looking straight into his eyes.
He gently takes me into his arms. 'I decide to be the luckiest man on earth who can proudly show to the world how three hearts beat as one in two bodies!' he whispers softly in my ear.
I melt at his sincere words. I know very well that he is the last man on the planet to assume he can order about his wife or any other woman for that matter according to his whims and fancies. An ecstatic moment it is to know I have found my soul mate in the tall, naughty, young man standing beside me looking into my eyes with ardour.
Being doubly blessed is the overwhelming emotion I find myself reeling under - not because of my awesome gift of double hearts alone but also the realisation that the heart of the most awesome man on earth is ready to throb in unison with my two hearts. As I take the tennis racket in hand I feel a doubly strong joie de vivre rushing through my body and soul.


text:
What will your retirement look like?
Plan today for a prosperous tomorrow
Life Insurance: Protection with a Purpose
SIMON SAYS® Let us help you Put Your Future in Capable Hands
Logical analysis of a financial situation or plan from a tax perspective, to align financial goals with tax efficient strategy. The purpose of tax reduction strategies is to discover how to accomplish all of the other elements of a financial plan in the most tax-efficient manner possible.
Your specific investment decisions will depend on several factors: your age, tax bracket, risk tolerance, liquidity needs, investment time horizon and investment goals.
Financial independence during retirement is a goal that many of us desire but rarely plan for adequately. We can estimate what you need to maintain your current lifestyle at retirement.
Generally, the goals of estate planning are to provide for financial security in life and to maximize - given the client's goals and objectives - the estate for family and other heirs following death.
Elder law is a legal term coined to cover an area of legal practice that places an emphasis on those issues that affect the aging population.


text:
BOO! Hai lovelies! Guess what? It's almost Halloween awesome stuff always comes out around this time of year. All your spookies and scaries and cuties and funnies. Well I'd like to show you some awesomeness today that I just HAD to share. The Costume Ball started today which runs until November 1st at Midnight. Which let me tell you, there are some fabulous designers that have gotten together to create some some great designs just for this event! This pale gorgeous skin from Pink Fuel is just one of these designs. The blood tattoo and teeth are separate but those luscious red lips and gorgeously detailed skin are what I want to show you. It fit just perfect for this vampire look. And it's Pink Fuel! One of my favorite skin designers so I would run down and demo this one because I can almost guarantee you will not walk away empty handed hehe!
Second I would love to show you this sexy but dark Black Widow dress made by Happy Undead. It's also available at The Costume Ball and it's mesh so the fit and move is just perfect! It comes with 18 different sizes and several different modifiable alphas so your avi can have the perfect fit! Go try it for yourself. Whether it be for a dark night out or to dress up for this Halloween this dress is perfect!
Exile released some new hair this past weekend and of course it's some beautiful Mesh styles! This one called Catch My Breath is definitely one I couldn't catch my breath over. I ended up walking out of the store with a whole pack! The style is perfect for a cute and casual look or even a formal dressy look! Go try to for yourself and find you favorite color!
Happy Shopping!
❤ Dani
Skin: Pink Fuel – Alyx – Ivory – Siren (light brow) **@ Costume Ball**
Blood: Pekka – Mouth Bleed tattoo layer
Teeth: Heartsick – Vampire Fangs (Found on marketplace)
Shape: Dani & Co.
Hair: Exile – Catch My Breath – MESH – Ember – Natural Fusions **NEW**
Flower: Pididdle – Ceramic Flower Headpiece – Rose **@ My Attic**
Dress: Happy Undead – Black Widow Mesh Dress **@ Costume Ball**
Cigarette: BOOM – Golightly Cigarette Stem – Espresso **@ Cinema**
Eyes: Insufferable Dastard – Steampunk – Clear – Mesh **@ Cinema**
Lashes: Redgrave – ExtraLong
Pose/Prop: .evolve – The Puppeteer **@ Costume Ball**


text:
Revealed today in Marvel Comics' Ultimate Fallout Issue 4: The new Spider-Man in the Ultimate universe is a half-Black, half-Latino teen named Miles Morales, reports USA Today. The famous Peter Parker was killed off by the Green Goblin in "Ultimate Spider-Man" No. 160 this summer.
In his first appearance, he simply breaks up a fight. But readers will learn the true origin of Morales and how he became the new Spider-Man when Ultimate Spider-Man relaunches in September with a new No. 1 issue. "The theme is the same: With great power comes great responsibility," says writer Brian Michael Bendis. "He's going to learn that. Then he has to figure out what that means."
In addition to an alliterative name, Miles has a connection to his predecessor in how he received his powers. But he will have different abilities, too. Supporting characters such as Peter's Aunt May and Gwen Stacy also will give Miles nuggets of wisdom to help his transition from young kid to New York City superhero.
More possible changes in the reboot: "Italian artist Sara Pichelli, who was integral in designing the new Spider-Man's look, says, 'Maybe sooner or later a black or gay — or both — hero will be considered something absolutely normal.'"
Bendis says the change is long "overdue." Even though there's some "amazing African-American and minority characters bouncing around in all the superhero universes," the comic writer says. "It's still crazy lopsided."
Marvel's "Ultimate" universe is separate from it's larger universe of characters, where Peter Parker remain alive and well. Given the history and interaction between Blacks, Puerto Ricans and Dominicans in New York City, the blatino Spidey reboots is spot-on.


text:
Your shopping basket is empty!
Enjoy it in a Martini, or if you prefer a longer, refreshing serve, try it in a classic G&T with Lamb and Watt tonic.
0 reviews / Write a review
So the story goes from Shed 1 Distillery that whilst dog walking on a wintry beach thoughts turned to hazy, summer days in the sun, frolicking around on the sand.
A luxuriously smooth gin, the initial sweetness gives way to juniper and floral notes that come from the elderflower we use, the silky liquor giving a warming finish.
A unique blend of wild juniper and botanicals, gathered from the Lakeland Fells under a full moon.
Made using 18 botanicals including elderflower, chamomile, grapefruit, sweet and rich Macedonian juniper and locally foraged wild Fife gorse which gives the gin its name.


text:
Costella Planner 2012
Made in USA
de Costella handbags Made in USA
Este es el precio que tus clientes ven. Editar lista de precios
Acerca del libro
Características y detalles
- Categoría principal: Libros de arte y fotografía
Características: 15×23 cm
N.º de páginas: 134
- Fecha de publicación: nov. 14, 2011
Acerca del creador
Costella handbags are the creation and artwork of Brazilian designer and photographer Luciana Ellington. With an impeccable eye for design, color, and style, Luciana infuses elements of her personal lifestyle into her handbags. Growing up as a competitive skateboarder in Brazil, Luciana still finds the pastime an influence of her design; vibrant color palettes, much like those of the graffiti in the streets, and textures, whether in the fabrication or the hardware. Making the move to the United States has only broadened Luciana's talent and gave her a new source of inspiration. Costella handbags exude a sensibility for casualwear that easily makes the transition into high fashion. A strong believer that anything worn on the body should be intuitive to your lifestyle, you will find Costella handbags to be a direct reflection of Luciana's passions. The Costella woman is edgy and confident with a unique taste for fashion and a keen sense of travel. The handbags are now sold throughout the


text:
Just over two hundred earth pounds for a 22-inch widescreen monitor looks like staggering value for money, in theory. But has Belinea cut any corners in practice with this monitor? In a word, yes. The most obvious casualty is the deletion of digital connectivity.
That's leaves the 2225S1W with a single analogue VGA socket and allows it to sneak under the UK DVI and HDMI import duty barrier. If that's a sensible compromise, the manifestly mediocre TN Film LCD technology is less welcome.
Only the cheapest panels suffer from noticeable light bleed these days, so you know there's some barrel scraping going on when you spot the bright patches at the top and bottom of the panel. Overall, the 2225S1W's washed out image quality and lack of vibrancy adds up to something of a false economy.


text:
2nd Gear Member
Last Activity: 07-01-2019 10:12 PM
About Me
- About DIRT_Racer
- Location
- Dunnville
- My car
- 84 318i
- Occupation
- Cement Mixer Driver
See the #90 DIRT 318i @ www.facebook.com/brewstermotorsports
DIRT is for racing, Pavement is for getting there. The only way to turn left, is to turn the wheel RIGHT!!
Locked Your DIff and hate it?
Give me a shout, will buy em up cheap, DIRT tracks are the ONLY place for a welded diff!!


text:
Luxury iPad Cases
Fall is the time for two things: fashion and Apples. Put them together and what do you get? iPads. The latest iPad is likely to take the stage in Cupertino on October 22. It's proven to be much more than a trend.
Apple's iPad is the tablet that made people finally lust after tablets. Up until the iPad Apple's competitors flogged them and failed; no one gave them a second glance. But ever since the iPad's introduction, people have been clamoring for them.
The iPad has that "it" factor, making it a darling of the fashion world. And why not? It's super slim, acts as a personal assistant, and conveys that coveted je ne sais quoi. But toting it around in a standard-issue case? A bit of a faux pas.
What to wear, though? It's your job to play stylist to your iPad and though it won't be sashaying down any red carpets, it will be seen on your arm. You don't necessarily need a bespoke iPad case like Karl Lagerfeld uses to protect his Computer Choppers white-gold iPad 2. (That's just one of the 30 to 40 iPads he has, according to his estimates.) Still, you want your case to stand out from the crowd.
So while you're running around town in Jimmy Choos or Christian Louboutins, your iPad can too. If you've got room in your Louis Vuitton Neverfull, you can slip your iPad in there, unharmed in a matching monogrammed case. Some designers, like Jack McCollough and Lazaro Hernandez of Proenza Schouler and Marc Jacobs, are even a step ahead, creating bags with room not just for your iPad but other belongings too.
We've shopped around to find you the most stylish luxury iPad cases, whether you're putting them in your shopping cart or on your wish list.


text: Cross Browser Debugging integrated into Visual Studio with BrowserStack January 31, '13 Comments [18] Posted in ASP.NET | VS2012 Sponsored By TL;DR - Too Long Didn't Read Version BrowserStack Integrated into Visual Studio From a debug session inside Visual Studio 2012 today with ASP.NET 2012.2 RC installed. Click the dropdown next to your Debug Button, the click on "More Emulators" to go to http://asp.net/browsers and get the BrowserStack Visual Studio extension and three months free service. There's other browsers to download as well, like the Electric Plum iPhone/iPad simulator. SIDE NOTE: When the VS2012.2 Update is finalized, you'll need to install just it and you'll get the ASP.NET Web Tools as well. New Online Tools for Modern Sites Head over to http://modern.ie for a bunch of tools for making cross browser sites easier, including on online site analyzer and downloadable Virtual Machines for any Virtual Platform. I do a lot of cross-browser testing and I've been on a personal mission to make "Browse With..." and multiple browser debugging suck less in Visual Studio. This has been going on for years. In 2010, I used PowerShell and hacked together a browser switcher script in VS2010. My buddy Kzu and friends saw this script, realized it sucked and made things better on VS2012 with their Default Browser Switcher addon. I worked with Jorge on our team and we delivered a the browser switcher dropdown directly integrated in VS2012. This feature is also in WebMatrix. Later the iPhone/iPad local simulator from Electric Plum added tight integration with Visual Studio so you can test locally. But still, it's too hard. There's been some Virtual Machines up on the Microsoft Download Center but it's tedious to dig around and get the one you need. BrowserStack Today the IE team announced new site at http://modern.ie to make cross-browser testing easier. Even cooler, they launched a partnership with BrowserStack.com to give us all a three month free trial to their hosted browser virtualization service. BrowserStack has a cloud of virtual machines with every browser imaginable. You can pick your OS, browser version and screen resolution, then effectively VNC (Remote) into them with their Flash plugin. It's totally seamless and really cool to see. Here you can see how hideous my site is in IE6 on Windows XP running within BrowserStack. Keep reading, it gets better. Well, IE6 doesn't get better, but this story does. Integrating BrowserStack with Visual Studio 2012 Even better, I noticed that BrowserStack has nice hackable URLs like this: http://www.browserstack.com/start#os=Windows&os_version=XP&browser=IE&browser_version=6.0&zoom_to_fit=true&url=hanselman.com&resolution=1024x768&speed=1 When I saw how clear it was, I immediately started writing a Visual Studio plugin - like within 5 minutes - then stopped after a half hour. I said, this is too obvious. Someone has already done written this, right? I google. Yes, they beat me to it, 5 days ago. BrowserStack already has a lovely Visual Studio Extension up and ready to go. It adds BrowserStack as a new browser choice within your Visual Studio 2012 debug dropdown. Start Debugging, pick my OS and Browser, in this case, Safari on a Mac running Mountain Lion. After you sign into BrowserStack with an account, you can setup a tunnel (using Java, but you can do it from the command line if you don't want to use an applet) between your local web server and BrowserStack and even debug in the cloud. Fabulous. After I've setup this tunnel, here I am debugging a website running local via a remote Mountain Lion Mac running Safari 6. Or whatever. You get the idea. Here am I at a breakpoint. Ya, it's freaking me out also. Again, if you've got VS2012, can you get this now any number of ways. You can go to http://asp.net/browsers, you can go to http://modern.ie or you can just click "More Emulators" within Visual Studio itself. Have fun! About Scott Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author. About Newsletter Sponsored By Hosting By Comments [18] Share on: Twitter, Facebook, Google+ or use the Permalink


text:
LiveSlideShow 2.0
LiveSlideShow provides all the tools you need to create a slide show with your favorite images with sound, visual transitional effects, and button navigation.
You can even add narration.
LiveSlideShow features 3 sections that make it easy to create the finished production:
- Section 1: drag-and-drop your pictures, graphics, navigation buttons,sound effects and narration clips into the media library.
- Section 2: drag clips from the media library into the timeline area;arrange them in whatever order you like; add transitions and captions.
- Section 3: position everything to your liking on the stage.
After creating your slide show, you can preview it to see if you need to make changes in images, sounds, or effects. After you are satisfied with your creation, you can post it on a Web site, e-mail it to friends and family, or, if it is job-oriented, present it at work. Your show is in a single file that can be read by anyone with the QuickTime Player. In addition, because LiveSlideShow is a QuickTime-based product, shows created with it can be shared between Mac and Windows platforms.
Please read the documentation or visit the home page for more detailed information.
System Requirements: A Power Macintosh running at 266MHz or faster; MacOS 8.5 or later; QuickTime 4 or later; 15MB of hard disk space for installation; 10MB of RAM free for the application.


text:
Get DVD Talk Feeds
Sex, sin, and Catholic guilt. If there's a better recipe for cinematic troublemaking, I don't want to know about it. "Into Temptation" dives into the deep end of collar-tightening, rosary-fingering unrest, creating a riveting momentum as it looks to articulate the push and pull between the obligations of religion and the overwhelming sway of sexuality. Sharply constructed with a heavy spray of noirish aroma, "Into Temptation" is a uniquely accomplished indie film, wielding salacious material sensitively, building an intoxicating sense of intrigue and discomfort.
Slightly bored with his daily business as a priest, Father John Buerlien (Jeremy Sisto) finds the arrival of a prostitute named Linda (Kristin Chenoweth) in his confessional captures his curiosity. Asking for absolution before she attempts suicide, Linda takes off into the night, leaving John consumed with finding her. Delving into the seedy underbelly of the city, John questions a series of unsavory types to learn more about this mysterious woman entangled in his every thought. Linda, on a crash course with death, seeks her own peace, confronting the violations of her life as she prepares for the end.
It's a difficult proposition to craft a film concerning a priest dealing with his celibacy in the growing shadow of everyday lust. Writer/director Patrick Coyle treats the soulful disturbance with tremendous care, shaping a tale of obsession that's soothing in surprising ways and utterly respectful of its characters. It's terrific filmmaking that winds John's distress methodically, observing the priest shaken out of the coma of his daily life by Linda's confession, finding urges submerged long ago creeping back into his thoughts, challenging the rigidity of his heavenly devotion. In the great tradition of high drama, Coyle muddies the water further with the introduction of Nadine (played vibrantly by Amy Matthews), John's one and only girlfriend, who has returned decades later, hopeful to reignite their love affair.
Coyle allows his actors marvelous scenes of introspection, gathering these silent moments to nurture a pensive mood of deliberation as John and Linda contemplate their life-changing choices. Of course, this retrieves career-best work from Sisto (wonderfully torn and aware), while Chenoweth is permitted an unusually grim role she's handles beautifully. Linda isn't a one-note lady of the night, but a damaged, abused soul electing to end a lifelong series of betrayals and numbing sexual interactions. Chenoweth is raw and real, shaping a devastating portrait of emotional submission limping to the end. Thankfully, Coyle doesn't push the cast into melodramatic nonsense, maintaining a nice edge of authenticity to the reactions and generous meditation that goes on during the film.
The anamorphic widescreen (1.78:1 aspect ratio) presentation on the "Temptation" DVD leaves much to be desired in the color department, with skintones almost blending into the background, draining the human character out of the film. The rest of the disc seems reasonably detailed and moody, with street scenes benefiting from strong shadow detail, creating a stronger sense of the mystery at hand.
The 5.1 Dolby Digital sound mix here is mild, but effective, working between jazzy tones of investigation and the opportunity for reflection. Dialogue is direct and pushed up front, with everything easy to understand. Club and city street sequences add nice surround atmosphere, opening up the story a little more than expected. Basic work, but it's good. A 2.0 track is also available.
English SDH and Spanish subtitles are offered.
Magnificently shot by cinematographer David Doyle (who turns happy-go-lucky Minneapolis into an imposing den of sin) and backed by a soft jazz score by Russell Holsapple, "Into Temptation" renders John's mission as a classic detective story of sorts, creating workable mystery and threat as John plunges further into immorality to chase clues, frightening his congregation and startling his confidant (Brian Baumgartner). Coyle attempts to tie it all neatly together in the end, and while I wasn't convinced by the outcome, the journey there is tremendously satisfying, reinforced by superbly confident filmmaking.


text:
Oh, hey, look what China did, again. Isn't this supposed to be an act of war now?
Massive Global Cyberattack Targeting U.S., U.N. Discovered; Experts Blame China
The world's most extensive case of cyber-espionage, including attacks on U.S. government and U.N. computers, was revealed Wednesday by online security firm McAfee, and analysts are speculating that China is behind the attacks.
The spying was dubbed "Operation Shady RAT," or "remote access tool" by McAfee — and it led to a massive loss of information that poses a huge economic threat, wrote vice president of threat research Dmitri Alperovitch.
. . .
Analysts told The Washington Post that the finger of blame for the infiltration of the 72 networks — 49 of them in the U.S. — points firmly in the direction of China.
See also:
Revealed: Operation Shady RAT
McAfee's Operation Shady RAT exposes national cybersecurity lapses
McAfee discovers massive series of cyber attacks
Hacking Campaign Targets U.S. Government, Signs Point to China
Operation Shady RAT: five-year hack attack hit 14 countries
China Suspected Of Shady RAT Attacks
Q+A: Massive cyber attack dubbed "Operation Shady RAT"
Operation Shady RAT: A frightening web of global cyber-espionage
Operation Shady RAT smells like Chinese hacking
All cursors point to China in global hack attack that threatens nations
China accused of biggest ever global cyber spying attacks
Hackers Based in China Attack UN, Olympic Networks, Security Firms Report
Operation Shady RAT and the cyberhacking
APT Attackers Used Chinese-Authored Hacker Tool To Hide Their Tracks
Why did it take a private security company to uncover the largest case of cyberspying in world history and why aren't we doing something about it?
/does China have to steal every last piece of sensitive and secret computer data we possess before we start taking this threat seriously?
Filed under: Blog Entry | Tagged: Analysts, Attack, Attacks, Blame, Case, China, Chinese, Computers, Cyber Espionage, Cyberattack, Direction, Discovered, Dmitri Alperovitch, Dubbed, Economic, Economic Threat, Experts, Finger Of Blame, Firmly, Global, Government, Huge, Huge Economic Threat, Infiltration, Information, Loss, Massive, Massive Global Cyberattack, Massive Loss, McAfee, Most Extensive, Networks, Online, Online Security Firm, Operation, Operation Shady RAT, Points, Points Firmly, Poses, Rat, Remote Access, Remote Access Tool, Research, Revealed, Security, Security Firm, Shady RAT, Speculating, Spying, Targeting, Threat, Threat Research, Tool, U.N., U.N. Computers, U.S., U.S. Government, United Nations, United States, Vice President, Vice President Of Threat Research, Washington Post, World's Most Extensive Case | Leave a comment »


text:
This is an automated email from the git hooks/post-receive script. t r a n s i f e x p u s h e d a c h a n g e t o b r a n c h m a s t e r in repository xfce/libxfce4util.
from 56e9c3c I18n: Update translation ast (57%). new 4080ebc I18n: Update translation ast (57%). new 46c03ca I18n: Update translation uz (57%). The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: po/ast.po | 4 ++-- po/uz.po | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository. _______________________________________________ Xfce4-commits mailing list firstname.lastname@example.com https://mail.xfce.org/mailman/listinfo/xfce4-commits


text:
After a housing search that spanned four years and included numerous home viewings and countless real estate rumors, The Sydney Morning Herald reports that Russell Crowe and his wife, Danielle Spencer have finally landed a new home in Rose Bay, Australia. The Oscar-winning actor and his wife ponied up around $10.1 million for the 1909 mansion that for reasons we'll choose to explore another time is curiously named Te Puke. The two-story home aka Te Puke features six bedrooms, about 3,600 square feet, and an arts-and-craft-styled second floor that was added in 1927.
According to The Real Estalker, the couple have been searching down under for the perfect home since 2007. Most recently in December 2010, the duo were reportedly intensely close to purchasing the gargantuan estate of the former ambassador to France, John Spender and his ex-wife fashion designer, Carla Zampatti. The purchase never came to fruition.
U.S. & World
If the couple's arduous and time consuming housing hunt is eliciting even a glimmer of sympathy then you might want to know that Crowe and his wife still own two incredible Sydney-area residences. One is a $14 million penthouse in Sydney Harbor and the other is a outlandishly large 800-acre rural estate North of Sydney. Are you green with envy yet?
Copyright LXTVN - LXTV


text: Buy Two DVDs Get One FREE!! How Can I Celebrate Advent? -- Beth and Digger happily hear God's plan of salvation as they light the candles of their Advent wreath and mark the days until the coming of Emmanuel our "God With Us." How Can I Celebrate Halloween? -- Digger is a curious youngster who would like to join in on the Halloween festivities, but some of his friends say that celebrating Halloween is wrong. How Can I Celebrate Passover? -- A young Christian's introduction to the Seder.