text:
From PostgreSQL wiki
(Difference between revisions)
(→Optimizer / Executor: add item for hashing arrays)
Mastermind (Talk | contribs)
(add wiki url for updatable views)
|Line 781:
|Line 781:
* [http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php <nowiki>Updatable views</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php <nowiki>Updatable views</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg01746.php
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg01746.php
Revision as of 07:22, 14 June 2009
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.
- [D] Allow administrators to safely terminate individual sessions either via an SQL function or SIGTERM
- 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.
- 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.
- Auto creation of Partitions
- Re: Auto Partitioning Patch - WIP version 1
- Dynamic Partitioning using Segment Visibility Maps
- Named vs Unnamed Partitions
- Storage Model for Partitioning
- Declarative partitioning grammar
- http://archives.postgresql.org/pgsql-hackers/2009-03/msg00897.php
- http://archives.postgresql.org/pgsql-performance/2009-05/msg00005.php
- Todo:PartitionedTables
- 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()
- Allow custom variable classes that can restrict who can set the values
- Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles
- 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
- [D] Allow SSL client certificate names to be checked against the client hostname
- This is already implemented in libpq/fe-secure.c::verify_peer_name_matches_certificate() but the code is commented out.. Fixed in M. Hagander commit 2008-11-13
- 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
Alternatively or additionally supporting OCSP (online certificate security protocol) would provide real-time revocation discovery without reloading
- Allow automatic selection of SSL client certificates from a certificate store
- Add 'hostgss' pg_hba.conf option to allow GSS link-level encryption
- 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
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.
- [D] Issue a warning if a change-on-restart-only postgresql.conf value is modified and the server config files are reloaded
- 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
- 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
Statistics Collector
- [D] Reduce the frequency that the statistics file is written
- [D] Allow statistics file location to be user-configured
- [D] Allow statistics collector information to be pulled from the collector process directly, rather than requiring the collector to write a filesystem file twice a second?
- 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)
- 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
- [D] Fix server restart problem when the server was shutdown during a PITR backup
- [D] Recreate pg_xlog/archive_status/ if it doesn't exist after restoring from a PITR backup
- Allow archive_mode to be changed without server restart?
Data Types
- Reduce storage space for small NUMERICs
- Add support for public SYNONYMs
- Fix CREATE CAST on DOMAINs
- Allow domains to be cast
- Make domains work better with polymorphic functions
- Add support for SQL-standard GENERATED/IDENTITY columns
- Improve XML support
- Consider placing all sequences in a single table, or create a system view
- [D] Allow the UUID type to accept non-standard formats
- Consider a special data type for regular expressions
- Reduce BIT data type overhead using short varlena headers
- Allow xml arrays to be cast to other data types
- [D] Simplify integer cross-data-type operators
- Allow adding/renaming/removing enumerated values to an existing enumerated data type
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] Extend timezone code to allow 64-bit values so we can represent years beyond 2038
- [D] Use LC_TIME for localized weekday/month names, rather than LC_MESSAGES
- [D] Add ISO INTERVAL handling
- [D] Support ISO INTERVAL syntax if units cannot be determined from the string, and are supplied after the string
- The SQL standard states that the units after the string specify the units of the string, e.g. INTERVAL '2' MINUTE should return '00:02:00'. The current behavior has the units restrict the interval value to the specified unit or unit range, INTERVAL '70' SECOND returns '00:00:10'. For syntax that isn't uniquely ISO or PG syntax, like '1' or '1:30', treat as ISO if there is a range specification clause, and as PG if there no clause is present, e.g. interpret '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and interpret '1:30' as '1 hour, 30 minutes'. This makes common cases like SELECT INTERVAL '1' MONTH SQL-standard results. The SQL standard supports a limited number of unit combinations and doesn't support unit names in the string. The PostgreSQL syntax is more flexible in the range of units supported, e.g. PostgreSQL supports '1 year 1 hour', while the SQL standard does not.
- Round or truncate values to the requested precision, e.g. INTERVAL '11 months' AS YEAR should return one or zero
- [E] 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
- [D] Delay resolution of array expression's data type so assignment coercion can be performed on empty array expressions
- 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
- [D] Fix to_date()-related functions to consistently issue errors
- Add missing parameter handling in to_char()
- Allow substring/replace() 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
- [D] Improve to_timestamp() handling of AM/PM, and error messages
- [D] Allow SQL-language functions to return results from RETURNING queries
- 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
- Add missing operators for geometric data types
- Some geometric types do not have the full suite of geometric operators, e.g. box @> point
- [D] Implement Boyer-Moore searching in strpos()
- 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
- [D] Add temporal versions of generate_series()
- [D] Add array_agg() and UNNEST functions for arrays
- 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] Fix all set-returning system functions so they support a wildcard target list
- SELECT * FROM pg_get_keywords() works but SELECT * FROM pg_show_all_settings() does not.
- Add has_sequence_privilege()
- Improve formatting of pg_get_viewdef() output
Multi-Language Support
- [D] Allow locale to be set at database creation
- Currently locale can only be set during initdb. No global tables have locale-aware columns. However, the database template used during database creation might have locale-aware indexes. The indexes would need to be reindexed to match the new locale.
- 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
- http://archives.postgresql.org/pgsql-hackers/2008-07/msg00557.php
- Todo:Collate
- Todo:ICU
- http://archives.postgresql.org/pgsql-hackers/2008-08/msg01362.php
- http://archives.postgresql.org/pgsql-hackers/2008-09/msg00012.php
- http://archives.postgresql.org/pgsql-hackers/2008-10/msg00868.php
- Unicode collation algorithm
- Add a LOCALE option to CREATE DATABASE, as a shorthand
- Add URL to more complete multi-byte regression tests
- Fix ILIKE and regular expressions to handle case insensitivity properly in multibyte encodings
- 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
- Another issue is whether underlying table changes should be reflected in the view, e.g. should SELECT * show additional columns if they are added after the view is created.
- 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 manager 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.
- Improve ability to modify views via ALTER TABLE
- Enable creation of RETURNING rules on inherited tables that have dropped columns
SQL Commands
- Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
- [D] Add a separate TRUNCATE permission
- Currently only the owner can TRUNCATE a table because triggers are not called, and the table is locked in exclusive mode.
- Change TRUNCATE to operate on an inheritance hierarchy by default, and add ONLY support to affect a single table
- [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 queries prepared via the libpq API are planned on first execute using the supplied parameters --- 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. This is similar to UPDATE, then for unmatched rows, INSERT. Whether concurrent access allows modifications which could cause row loss is implementation independent. To implement this cleanly requires that the table have a unique index so duplicate checking can be easily performed. It is possible to do it without a unique index if we require the user to LOCK the table before the MERGE.
- Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
- Enable standard_conforming_strings by default in 8.6?
- 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
- [D] Add SQL:2008 Common Table Expression (WITH [RECURSIVE]) clause to SELECT
- 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
- [D] Implement SQL:2008 window functions
- Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause or target list
- [D] Increase locking when DROPing objects so dependent objects cannot get dropped while the DROP operation is happening
- Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ... RETURNING to supply values to the INSERT
- Add comments on system tables/columns using the information in catalogs.sgml
- Ideally the information would be pulled from the SGML file automatically.
- [D] Improve reporting of UNION type mismatches
- 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.
- 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.
- Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message
- Have CREATE TABLE LIKE copy column storage parameters
- CREATE OR REPLACE FUNCTION might leave dependent objects depending on the function in inconsistent state
- Allow GLOBAL temporary tables to exist as empty by default in all sessions
- Add OR REPLACE to CREATE LANGUAGE
- Allow the creation of "distinct" types
- Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
- Research self-referential UPDATEs that see inconsistent row versions in read-committed mode
- 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.
- [D] Prevent parent tables from altering or dropping constraints like CHECK that are inherited by child tables unless CASCADE is used
- [D] Prevent child tables from altering or dropping constraints like CHECK that were inherited from the parent table
- 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.
- [D] Consider using a ring buffer for COPY FROM
- 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
- Impove COPY performance
- Allow COPY to report errors sooner
- Improve bytea COPY format
- [E] 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;
- 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
- 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.
- 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.
- Allow multiple identical NOTIFY events to always be communicated to the client, rather than sent as a single notification to the listener
- Improve LISTEN concurrency
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.
- The cases we support now are basically those where no row ever exits the frame as the current row advances. To do better requires some rethinking of the window aggregate support.
- 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
- Allow DEFERRABLE and end-of-statement 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
- [E] Report the schema along table name in a referential failure error message
Server-Side Languages
- Fix RENAME to work on variables other than OLD/NEW
- 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.
- Review handling of MOVE and FETCH
- Improve logic of determining if an identifier is a a variable or column name
- Consider keeping separate cached copies when search_path changes
- Improve pl/pgsql's ability to cope with rowtypes containing dropped columns
- [D] Add CASE capability to language (already in SQL)
- [D] Add translations for PL/pgSQL error messages
- Improve handling of NULL row values vs. NULL rows
- Rethink memory management for simple expression evaluation
- [D] Consider honoring standard_conforming_strings in function bodies
- Add PL/PythonU tracebacks
- Add support for Python 3.0 to PL/Python
- Allow data to be passed in native language formats, rather than only text
- 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.
- Add a function like pg_get_indexdef() that report more detailed index information
- 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
- [D] Have \d show foreign keys that reference a table's primary key
- [D] Have \l+ show database size, if permissions allow
- Ideally it will not generate an error for invalid permissions
- 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
pg_dump / pg_restore
- [E] Add dumping of comments on index columns and 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.
- 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.
- 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.
- [D] Allow pg_restore to utilize multiple CPUs and I/O channels by restoring multiple objects simultaneously
- This might require a pg_restore flag to indicate how many simultaneous operations should be performed. Only pg_dump's -Fc format has the necessary dependency information.
- Allow pg_restore to create all indexes of a table concurrently, via a single heap scan
- This requires a pg_dump -Fc file because that format contains the required dependency information.
- [D] Prevent pg_dump/pg_restore from being affected by statement_timeout
- Using psql to restore a pg_dump dump is also affected.
- 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
- Have pg_dump -C emit ALTER DATABASE ... SET commands after database creation
- Allow parallel restore of tar dumps
- Docs
- Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.
- 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 severity to PGconn return status
- Fix libpq initialization to play nicely with applications that use libcrypto but not libssl
- It's not entirely clear if we should just fix the immediate problem, or try to provide some more general solution for controlling libpq initialization.
- Make libpq thread-safe in programs that use fork()
- This requires the use of pthread_atfork() to release global locks held in libpq
- Add deferred trigger queue file
- 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, or some bulk operation.
- 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
- 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
- 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.
- [D] Require all CHECK constraints to be inherited
- [D] Add checks to prevent a CREATE RULE views on inherited 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.
- Allow accurate statistics to be collected on indexes with more than one column or expression indexes, perhaps using per-index statistics
- [D] Increase the default and maximum number of statistics targets
- 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, and have pg_restore use it
- 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
- Support queries that require a full scan
- 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] Consider sorting hash buckets so entries can be found using a binary search, rather than a linear scan
- Improve information_schema's entries for precision and scale
- [D] Consider using hash buckets to do DISTINCT, rather than sorting
- This would be beneficial when there are few distinct values. This is already used by GROUP BY.
- 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
- Improve speed with indexes
- For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the indexes. Also, this situation 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
- [D] Create a bitmap of pages that need vacuuming
- Instead of sequentially scanning the entire table, have the background writer or some other process record pages that have expired rows, then VACUUM can look at just those pages rather than the entire table. In the event of a system crash, the bitmap would probably be invalidated. One complexity is that index entries still have to be vacuumed, and doing this without an index scan (by using the heap values to find the index entry) might be slow and unreliable, especially for user-defined index functions.
- 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
- [D] Improve dead row detection during multi-statement transactions usage
- 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
- [D] Improve control of auto-vacuum
- 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.
- [D] Store per-table autovacuum settings in pg_class.reloptions.
- Prevent autovacuum from running if an old transaction is still running from the last vacuum
- 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
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
- 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
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)
The above patch is already applied as of 8.4, but it still remains to figure out how to handle plain indexscans effectively.
- 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
- Expire published xmin for read-only and idle transactions
- Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call
- [D] Improve performance of shared invalidation queue for multiple CPUs
- 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
- Information schema performance improvements
Miscellaneous Other
- Deal with encoding issues for filenames in the server filesystem
- Deal with encoding issues in the output of localeconv()
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.
- http://archives.postgresql.org/message-id/19934.1226601952%40sss.pgh.pa.us
- http://archives.postgresql.org/pgsql-hackers/2008-10/msg00002.php
- http://archives.postgresql.org/pgsql-hackers/2008-10/msg01028.php
- http://archives.postgresql.org/pgsql-hackers/2008-11/msg00524.php
- http://archives.postgresql.org/pgsql-hackers/2008-12/msg01101.php
- Improve the module installation experience (/contrib, etc)
- Update Bonjour to work with newer cross-platform SDK
- Allow creation of universal binaries for Darwin
- Consider GnuTLS if OpenSSL license becomes a problem
- [D] Update our code to handle 64-bit timezone files to match the zic source code, which now uses them
- [D] Have configure choose integer datetimes by default
- Support scoped IPv6 addresses
- [D] Consider allowing 64-bit integers and floats to be passed by value on 64-bit platforms
- Also change 32-bit floats (float4) to be passed by value at the same time.
- Research use of signals and sleep wake ups
- 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
- [D] Remove use of MAKE_PTR and MAKE_OFFSET macros
- Create three versions of libpgport to simplify client code
- [D] Remove old-style routines for manipulating tuples
- 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
- Fix system views like pg_stat_all_tables to use set-returning functions, rather than views of per-column functions
- 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
- Add support for returning multiple result sets?
- Restructure TOAST internal storage format for greater flexibility
- 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
- 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
- [D] Prevent SSL from sending network packets to avoid interference with Win32 signal emulation
- Fix MSVC NLS support, like for to_char()
- Find a correct rint() substitute on Windows
- 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
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
- Bringing PostgreSQL torwards the standard regarding case folding
- Re: [SQL] Case Preservation disregarding case sensitivity?
- TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers
- Identifier case folding notes
- http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php
- Add autonomous transactions
- Give query progress indication
- Rethinking 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.
- Optimizer hints (not wanted)
- Optimizer hints are used to work around problems in the optimizer. We would rather have the problems reported and fixed.
- 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.
- 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. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.


text:
Skip to main content
Sarah replies:
Manual sex feels fine but anal sex really hurts me. And my boyfriend use lots of lubricant but my ass really hurts during and after anal sex. Why does anal sex hurt so much?
Anal sex, or ANY type of sex for that matter, isn't going to be the "bee's knees" for everybody. Even if one sexual activity feels good, that's no guarantee that every type of sex is going to feel good either. It may just be that anal sex is not really your thing, and that's okay. Not everybody likes it.
There are some things that you can do to make sure that any anal sex you are trying to have is more likely to succeed.
You may also want to check out:
Information on this site is provided for educational purposes. It is not meant to and cannot substitute for advice or care provided by an in-person medical professional. The information contained herein is not meant to be used to diagnose or treat a health problem or disease, or for prescribing any medication. You should always consult your own healthcare provider if you have a health problem or medical condition.

subset: commoncrawl


text:
Thoughts for the New Year
Posted by Cynthia | Filed under Musings
Earlier this year the AIGA interviewed John C. Jay, Wieden+Kennedy's executive creative director. He offered "10 Lessons for Young Designers". I saved this list and revisited it recently. It seems especially appropriate at this time, as we consider the passing of the current year, and look ahead to self awareness and improvement as we embark on 2012. I believe this list is broader than its title, and is applicable not only to young designers, but to a person of any age or occupational discipline. We can all benefit from John's words of wisdom.
1: Be authentic. The most powerful asset you have is your individuality, what makes you unique. It's time to stop listening to others on what you should do.
2: Work harder than anyone else and you will always benefit from the effort.
3: Get off the computer and connect with real people and culture. Life is visceral.
4: Constantly improve your craft. Make things with your hands. Innovation in thinking is not enough.
5: Travel as much as you can. It is a humbling and inspiring experience to learn just how much you don't know.
6: Being original is still king, especially in this tech-driven, group-grope world.
7: Try not to work for stupid people or you'll soon become one of them.
8: Instinct and intuition are all-powerful. Learn to trust them.
9: The Golden Rule actually works. Do good.
10: If all else fails, No. 2 is the greatest competitive advantage of any career.
Best wishes for the New Year.
Image: AIGA
Tags: 10 Lessons for Young Designers, AIGA, Graphic Design, interior design, John C. Jay, New Years Resolutions, Wieden + Kennedy


text:
Call Us Toll-Free @ 866-539-4278866-539-4278
Creative Crafthouse puzzles are fantastic brain teasers made from wood that are fun for kids and adults of all ages. They have many types to choose from, several which are unique to Creative Crafthouse... designed and made here in the USA.
Use the filters to the left or simply scroll down to begin viewing all pages.
Copyright © 2015, Puzzle Warehouse, All rights reserved. St. Louis Jigsaw Puzzles
Puzzle Warehouse recycles everything it can to save the environment and to keep costs and prices low.


text:
Log in
On a walk through downtown Kalamazoo, one would be hard pressed to fail to take notice of both the number and variety of works of public art which adorn building facades, walkways, parks, and even alleys. After completion of a photo gallery dedicated to public sculpture in Kalamazoo, the idea of creating a similar gallery of public murals came up and immediately appealed to me. One of the tasks that I have enjoyed the most as the local history room intern has been the exploration and documentation of the landscape of Kalamazoo through photography.
Once begun, the project began to swell beyond my initial impressions of the number of public murals to be found in Kalamazoo. Some murals have been present for decades and have become so well integrated into the cityscape that they have become easy to overlook. New murals are arriving annually, being painted by local artists such as Conrad Kaufman, who has made a name for himself in the region due to the sheer number of murals he has created for both public and private audiences.
While some of Kalamazoo's murals are easily located, others are more well hidden. Throughout the process of locating and documenting these works of art, I have often been surprised at what can be discovered through a slight variation of a routine route through town. After an examination of the murals in the photo gallery, it is my hope that you will seek them out on your own if should you happen find yourself nearby. If you are aware of any murals that are readily accessible to the public and have not yet been included in the gallery, please let me know in order to help make the list as complete as possible.
Posted by Patrick Jouppi at 06/26/2011 03:31:46 PM |


text:
this wiki
The Vapid NOOSE Cruiser is a vehicle featured in Grand Theft Auto IV.
The NOOSE Cruiser is the NOOSE variant of the Police Cruiser.
The NOOSE Cruiser shares the chassis of the Police Cruiser (based on a combination of Ford Crown Victoria's), albeit with an LED light bar in place of the Police Cruiser's spinning V-bar, and NOOSE livery rather than that of the LCPD. The LED light bar does not make a distorted sound after being crushed or shot at with a weapon like the Police Cruiser's/Patrol's V-bar.
The NOOSE Cruiser is called out when a 3-star Wanted level is attained, and is used to create roadblocks. The car serves roughly the same role as the NOOSE Patriot, which is called in at higher Wanted levels. The NOOSE Cruiser's livery is loosely based on the livery of Homeland Security vehicles. The livery also bears a passing resemblance to the New Jersey State Police livery, both containing blue and yellow vertical stripes.
In The Ballad of Gay Tony, the NOOSE Cruiser appears to spawn more often than in GTA IV when the player is being chased by the police. It even goes as far as to replace Police Cruisers, which are usually the designated pursuit vehicles.
Strangely, despite being a NOOSE issued vehicle, only regular police officers occupy it.
PerformanceWhen compared with the Police Cruiser, the NOOSE version appears to have undergone a pleasant array of upgrades. The engine feels as if it's breathing better, and its power band is improved dramatically. The suspension is firmer, the body roll is not as severe. Handling-wise, this huge car can match more performance-oriented cars, and stability at its top speed is vastly different from the standard Police Cruiser.
- When you hijack a NOOSE Cruiser without a wanted level, you will not gain a wanted level.
- When you steal a NOOSE Cruiser, the headlights will stay on whether it is night or day and the player can only switch them to high beam or low beam.
- On the side of the car, it says it is that it is from the Patriotism Immigration Authority. The fact that Niko is an immigrant could be the reason it chases him.


text:
methebest wrote:Callonia wrote:Callonia seems to have fallen in love with World of Tanks.
are you a terrible below 48%er?
I think I will just let my profile speak for itself.
http://worldoftanks.com/community/accou ... Ericridge/
Here it is. Enjoy.
Already have few ace tankers xD and lost a few ace tankers as well.


text:
Log in
Free college education...that's exactly what these Great Courses DVDs are.
Our library has about 25 of these; type in "great courses" as a "series" search to find them all. To get the many, many more that are out there, get them through MelCat with your KPL card! That's how I get most of mine. Again, type "great courses" as a "series title" search. Or you could ask us to buy one.
They also come in audiobook format (CD and cassette), for listening in your car or on your ipod. I cannot express how happy I am that these exist, and that libraries like ours have them. Any person with a library card can really know a lot about a lot of different subjects, in much less time and effort than ever. Carnegie, the great philanthropist, thought of libraries as great equalizers, places where poor immigrants could "catch up." Imagine what he would think of these! The old idea of the "renaissance man" is in some ways more real. These are taught by world renown professors, exciting, understandable. Older people love watching these to learn new things, keep their mind sharp, and brush up on things. Pre-college students love watching them to get a head start on everybody else. I wish I knew about these when I was younger!
Free college education (without the degree of course) is catching on more and more. Universities like Yale and MIT have posted several of their courses online, for free. Academic Earth is the Hulu for such video lectures.
Posted by Matt Smith at 02/18/2011 05:13:04 PM


text:
Everyone at the party will fall apart over how cute you look as the new ghoul at Monster High. You will have so much fun this Halloween as a fashionable and not-so-scary version of a monster in our Monster High Women's Frankie Stein Costume. Included is a dress, tie, tights, belt, and shoe covers. This plaid mini-dress with sheer black puff sleeves is already a lot of fun, but the addition of the studded belt and the attached polka-dot tie with the Monster High emblem will make people freak over how chic this outfit is. This ghoulish look goes all the way down to your toes too by slipping on the shoe covers that mimic Frankie's funky black and white striped shoes. Your transformation into will be complete with the pale green long sleeves and tights to give you the same stitched up accents like her own arms and legs. You may be grown up, but you can still have fun playing a little dress up with this sassy monster's look. There's no doubt that you will look totally cute and a little monstrous in your Frankie Stein costume.
Our Price: $3.97
Our Price: $29.99
Our Price: $4.99
Our Price: $19.97


text:
A man and a woman are dead after a single motor vehicle accident on the Monaro Highway about 14 kilometres out of Cooma on Wednesday.
The vehicle they were travelling in, a Toyota Hilux utility, rolled a number of times killing the driver from the ACT and his 42-year-old female passenger who was from Queanbeyan.
The accident occurred near Rock Flat Creek Bridge between Cooma and Nimmitabel at midday.
The highway was closed in both directions until about 3pm while emergency crews attended the accident.


text:
Refine your search by adding filters below. Click the red square to remove them. Add as many as you like.
Free weekly email packed with travel tips for major world cities, great competitions and exciting features.
Canada's most luxurious department store chain manages to feel more intimate than ever, despite the opening of these swish, multi-million-dollar, 12,700sq m...737 Dunsmuir Street
© 2016 Time Out Group Ltd and Time Out Digital Ltd. All rights reserved. All material on this site is © Time Out.


text:
Studded Velvet Ogee Pillow Cover - Iron
Act fast! Items with prices ending in $0.99 are final sale.
No longer available
Globalist with an edge. Deco-inspired, the patterned nailhead trim of our Studded Velvet Ogee Pillow Cover adds just the right measure of toughness to its ultra-soft finish.
100% velvet cotton in Iron.
Graphite-finished metal nailheads.
Zipper closure.
Accommodates an 18"sq. Pillow Insert (sold separately).


text:
Dave Dave HamburgerFollow Dave
28-year-old Male living in Old Bridge, New Jersey USA
Graduated from New Jersey City University with a Bachelors degree in finance. My 2 passions are hockey and the outdoors. I play hockey about 4 times a week, and enjoy going to the beach, kayaking, mountain biking, hiking, snowboarding, camping, and anything that is outside where I can enjoy nature! I'm very easy going, love to listen to music and go to concerts, make new friends, and enjoy life!
Level 1 Traveler
1 tour
1 country
Following 0 people
Followed by 1 person
Find me on
Discussions in order of recent activity
Dave is not following any discussions.


text:
Stacy Martin sits in a quaint salon at the offices of her U.K. talent agency. All of the prototypical English amenities are lying untouched on the glass table between us. She carries herself contentedly and appears self-assured, but with a certain underlying sense of wide-eyed wonderment—a demeanor to be expected, as she's only just begun the press rounds promoting her very first film, the incomparable Lars von Trier's latest, Nymphomaniac.
With 55 nude scenes in the can, a "porn double" on set (to stand in during hard-core penetration), and a prosthetic mold of her vagina now hanging around some prop house, the summation of her filmic experience reads like that of a seasoned art-house veteran, which makes the fact that this is her maiden performance all the more impressive. And while commercial viability never really enters the equation with Von Trier, expectations could not be higher as Martin's acting debut is slated for a two-part American release in March and April of this year.
Born and educated in Paris, though raised partly in Japan, the 23-year-old Martin seems either entirely unconcerned about or oblivious to the fact that she is poised to become a magnet for mainstream attention. And not just for the provocative nature of this role, but for her brilliant and compelling delivery as well. After five years sheltered by relative anonymity while modeling her way through college and acting classes, she netted the opportunity of a lifetime as the younger analogue to Charlotte Gainsbourg's Joe: a hypersexual antihero, fucking her way to retribution and freedom from the prevailing social contract of polite society. The story, told in eight chapters through flashback and narration, follows Joe on her journey from childhood libidinal awakening to a sort of postsexual enlightenment, with plenty of Oedipal conflicts, adolescent angst, and sadomasochism in between. It isn't just a film about sex or sex addiction. It's a film about how sex governs and acts upon the entirety of our existence, right down to the very last banality of home life.
Martin, for her part, is under no illusion about the nature of the business that gave her her start, to say nothing of its implicit correspondence with the subject of this film. "Maybe I have been exploited as a model. When you're a model, you're a hanger. You are objectified and you are used and then portrayed a certain way." What's most striking, however, about such a seemingly inflammatory remark is that Martin delivers it without the slightest hint of cynicism or contempt, conveying only mindfulness of how things work. Sure, the money's good, but it demands a palpable existential sacrifice to stand in for the aesthetic embodiment of some generic feminine persona, be it "the girl next door," "the grungy kid," "the sexy sophisticate," or "the weird, quirky girl." "It's playing on what culture says a woman is," Martin continues. And what culture says a woman is is exactly what Joe wants to destroy. These obsolete, hypocritical demands for both morally upstanding behavior and sex appeal are enough to drive anyone mad. Why can't a woman be free to be both the Madonna and the whore without fear of judgment?
"We as women give birth to everyone, but at the same time we're restricted, we have to act a certain way, and we have to fill a certain role," Stacy says, as if employing the subtext of Gustave Courbet's L'Origine du Monde (1866) to make her point. Forcing the world to confront its own collective duplicity is perhaps Lars von Trier's greatest strength as an auteur. Not since Freud published his case study on Dora has there been a more vivid example of hysteria and the ineffable rift between woman as subject and woman as object than in Nymphomaniac. This becomes especially apparent when considered within the context of Von Trier's other recent films, Melancholia and Antichrist. Unfortunately, as is often the case with his more defiant work, the biting nuance of his social commentary is often overlooked by an audience and media overly focused on the explicitness of its delivery. In Antichrist, for example—a tragic story about a mourning mother sadistically made to suppress her personal experience of grief according to the demands of an aloof husband turned psychoanalyst—the film's subtle psychology was overshadowed by a few shocking scenes of genital mutilation. If society insists on being so crass and vulgar as to reduce the idea of woman to the sum of her parts, the least it can do is acknowledge the staggering complexity that exists down there. But whether these ideas as brilliantly proffered by Von Trier in Nymphomaniac will overcome the film's graphic honesty remains to be seen.
A smiley young man enters the room to bring Stacy a tea, and on his way out kicks my umbrella by accident. He's quick to apologize and nervously stands it back up. But Stacy just as quickly makes a joke to lighten the mood and allay his embarrassment, a talent not without its value in her line of work, especially when you're spending long hours fully nude, simulating sex acts with men you've only just met in front of an entire film crew. The door closes behind him, leaving us alone again, and the irony of the situation dawns on me: after having finally finished working on such a physically and emotionally demanding film, she's now being asked to speak candidly with countless perfect strangers, such as myself, about her life—her real life. The complexity of this situation is not lost on Martin in the slightest, who is eager to talk about these types of serious subjects in hopes of providing a better understanding of the profound sense of alienation the film confronts.
Martin knew very well what Nymphomaniac was trying to say when she signed on to the project, and she remains passionate even now about wanting to deliver the message. This deep understanding is perhaps how she was able to keep such a positive outlook in spite of some of the more extreme physical demands of the role. There was never any expectation that filming numerous nude sex scenes—often more than one in the same day—was going to be an enjoyable experience. And it could yet emerge to have been a futile one, as these commentaries on gender bias and sexual oppression sometimes get lost in the fray of such shocking imagery. What carried her through the discomfort was her faith in Lars. "It was an amazing opportunity," she says, "and I just wanted to honor how good the script was." When I ask whether she found the filming to be coercive or exploitative (a clear allusion on my part to the controversy surrounding Abdellatif Kechiche's Blue Is the Warmest Color) Martin once again references her pragmatic approach to acting. "I just think, well, they are difficult scenes, you're not going to be laughing through them. I would feel empty after, and I would think to myself, Is this me as a person or is this me as the character? There's a really fine line. I wasn't ashamed to be tired or upset or angry. It's probably how [Joe] felt. It's difficult, but that's the process." Such an evolved perspective is impressive, and rare among first-time actors. This is likely something Von Trier too was able to identify in Stacy, seeing as this sort of bravery and openness are so crucial to the role.
The determination to be free from her oppressor by any means necessary sets Joe apart from the heroines of Von Trier's other films. Joe is not concerned with what the world thinks of her. Her only care is what she thinks of herself. Something not unlike what Stacy Martin has undertaken in accepting this role. Joe calls society cowardly and hypocritical, and has devoted her life to transgressing what the "morality police" deem obscene. Any attempt to identify herself with the outside world only ends up reaffirming her resolve to cut herself off from it once and for all. She acts according to what is right for her and her alone. Stacy, in turn, is building a career by taking the path less traveled, the one more timid individuals may have shied away from for fear of the negative perception it could bring. In both cases, what emerges is an affirmation of the subjective self in the face of societal prohibition, a blatant disregard for the judging eyes of others—something to which one cannot help but be attracted.
Jacques Lacan once theorized that "woman doesn't exist" but rather is only "the symptom of man." In a world as such, intent on the effacement of feminine subjectivity, where a woman's identity is conditioned by motherhood, matrimony, and sex appeal, true power comes in the refusal to further perpetuate false selfhood. Joe's journey in Nymphomaniac is that of a hysterical breakdown. In not being able to reconcile who she thinks she is with who she is expected to be, Joe can regain her subjectivity—her true autonomous identity—only by means of an irreversible break from society. Stacy Martin, for her part, seems to be following suit in engendering a similar idea of empowerment for herself. She too has broken from the comforts of the status quo, and is instead setting off into the unknown. "I really wasn't that person I thought I was," she says with regard to her exit from modeling to pursue what she felt would be a more fulfilling existence. The significance of not merely having such a realization but being strong enough to act on it, to set off in one's own way, on one's own terms, cannot be overstated. We will see more of Stacy in the future to be sure, but it will be as she wants, not as what we want from her.
Makeup Christine Corbel (Management Artists) Hair Olivier de Vriendt (ArtList) Manicure Kamel (B-Agency) Photo assistant Emmanuel Trousse Stylist assistant Oumeih Benaicha Production Backwall Retouching Maxime Lefebre Roque (Odalisques) Special thanks Le Carmen


text:
- TM63 Embargo D/P/Pt
- Coin Case D/P/Pt
- TM60 Drain Punch D/P/Pt
- HM02 Fly D/P/Pt
- TinyMushroom D/P/Pt
- Full Incense D/P/Pt
- PP Up D/P/Pt
- Revive D/P
- Rare Candy Pt
- Star Piece x2 Pt
- Calcium Pt
Veilstone Pokémon Gym
The road to get to the Gym Leader is not direct. There are several punching bags that you have to strategically push until the road is open to reach the Gym Leader.
- In Pokémon Platinum version, Veilstone City's design differs markedly to that of its predecessor games; namely, the Galactic Headquarters has been completely redesigned.


text:
Carolina Panthers
Got the official cap to show your Panthers Pride? Lids.com is your headquarters for Carolina Panthers hats, and all your favorite NFL team hats and accessories. Show your Panther pride anytime, anywhere with awesome Carolina Panthers T-Shirts. Do the dab with Cam Newton shirts or rock a Luke Kuechly jersey to the big game to show just which team is the best in the NFL!
Currently there are no products available...
Shop By
- Apparel & Accessories
- Auto Accessories
- BBQ & Grilling
- Bed & Bath
- Bobbleheads
- Bumper Stickers & Decals
- Cellphone Accessories
- Checkbooks, Wallets & Money Clips
- Collectibles
- Flags & Banners
- Gameday & Tailgate
- Golf
- Helmets
- Home Office & School Supplies
- Jewelry
Whats New


text:
Prices and availability are subject to change from the time and date that you print this page.
5/2/2016 8:49:48 AM. For Customer Service, please call 800.606.6252
neutral territory. Heathered natural wash creates variegated painterly effect, playing up nubby waffle-like bouclé texture. Handwoven on traditional looms, 100% cotton oblong flips to solid natural cotton. Do the math: CB2 low prices include a pillow insert in your choice of plush feather-down or lofty down-alternative (a rare thing indeed).
Details and Dimensions
format natural 23"x11" pillow with feather-down insert. 23"Wx11"D
- 100% cotton
- Front: printed bouclé
- Back: solid natural
- Feather-down insert: 95% white duck feather, 5% white down fill (made in Thailand)
- Down-alternative insert: 100% polyester fill (made in China)
- Color intensity and pattern will vary; each is unique
- Machine wash
- Made in India
Overall DimensionsWidth: 23" Depth: 11"
Return/Exchange Policy
At CB2, we stand behind the quality of our products and want every purchase to be a positive experience. We will do our best to make things right if you are not satisfied.
non-furniture items
We will accept returns and exchanges of non-furniture items if they are returned within 90 days of customer receipt, a valid proof of purchase is provided, and items are returned in good condition (unused and unwashed).
stock furniture, rugs and rug pads
If you are not satisfied with your Stock furniture, rug or rug pad purchase, you must contact us within 7 days of delivery or pickup to arrange a return. The item must be returned within 30 days of delivery or pickup. The item will be inspected upon return, and a refund amount will be determined based on its condition. For furniture orders placed online, please call us at 800.606.6252. For orders placed through a store, please contact the store where the sale originated.
special order upholstery
We require a 50% deposit for all Special Order upholstery. This deposit is nonrefundable after a 72-hour change/cancellation window. These items are made to your specifications and cannot be returned or exchanged.
Crate and Barrel Recommends
kabasa vase limited time $23.96reg. $29.95
paramount table lamp$59.95


text:
Simply Gorgeous!!
Created in: Inkscape and Gimp
Never let it be said that open source drawing programs are inferior to their paid for equivalents. The scale, detail and colour choices of Veuxin's map are magnificent.
The end result is quite stunning and original and shows just how multi-skilled the author of this map is. The number of applications used tells of the author's dedication to create an end result he was happy with. The artistic merit of the map is pure talent of conceiving a result in the mind's eye and realising it to exacting standards.
Original threadsOriginally Posted by Veuxin
Click here to view the Finished Map thread.
Last edited by ravells; 02-03-2011 at 05:05 AM.
Simply Gorgeous!!
Congrats on a gorgeous map! I love the crisp brightness of it, and the details are insane!
This is really a great map, good choice for the Featured hall of fame
When its over and you look in the mirror, did you do the best that you were capable of? If so, the score does not matter. But if you find that you did your best you were capable of, you will find it to your liking. -John Wooden
* Rivengard * My Finished Maps * My Challenge Maps * My deviantArt
Excellent! Repped!
"I do not know whether I was then a man dreaming I was a butterfly, or whether I am now a butterfly dreaming I am a man"
My Finished Stuff ............. Some of my 3D Stuff (POVRay)
Glad to see you're still checking in, crayons!
Checking in - Oh yes - bad penny syndrome! Lots of stuff been going on - some post-NY mapping burnout, Xmas, a laptop gone doolally (replaced - but Win7! Aaaargh!) and a commission (Oh lawks!) - but 's nuff about me - not here anyway (shush!).
Veuxin's produced a real corker here which seriously deserves the title of a Cartography Featured Map - as opposed to some of the cartoony rubbish lurking around here lately!!! I thought I should quip in quick so it looked like I was paying attention and wasn't just lucky I looked in today!
"I do not know whether I was then a man dreaming I was a butterfly, or whether I am now a butterfly dreaming I am a man"
My Finished Stuff ............. Some of my 3D Stuff (POVRay)
Wow, incredible work! Love the detail, the style - everything about this shows how much work you put into it. Bravo!
That's astounding, the attention to detail is quite amazing...
Truly amazing!


text:
The Power of Independent Thinking
Bush, Obama, and Presidential Power
Recorded: Wednesday, January 7, 2009
Ron Paul, Richard Shenkman, and Ivan Eland, author of Recarving Rushmore, discuss which presidents were the best and worst at promoting peace, prosperity, and liberty.
Experts: Ivan Eland, Ron Paul, Richard Shenkman, David J. TherouxType: TelevisionIssues: Defense and Foreign Policy, Government Power, History (U.S), Politics
Michael Crichton on States of Fear: Science or Politics?
Recorded: Tuesday, November 15, 2005
The late Michael Crichton, author of Jurassic Park and State of Fear, along with a panel of distinguished scientists, examine the increasing politicization of science.
Buy this event on DVD
Experts: Sallie Louise Baliunas, Michael Crichton, William M. Gray, George H. TaylorType: Independent Institute EventIssues: Energy, Environment, Science, Technology


text:
If you've been confused by the growing number of men showing off stubble this month, let me reassure you – it has little to do with the oncoming threat of snow.
It's Movember, a month where men grow moustaches to build awareness for prostate-cancer research.
And, I have to say, I'm in love.
No, I don't love the feeling of stubble on my cheek or have a quarter-life urge to take home a mountain man – despite recent findings by scientific journal Evolution and Human Behavior, which state that women see men with facial hair as more attractive than their clean-shaven counterparts.
In fact, I abhor stubble. But I'm in love with the simple fact that Movember has lightened up the act of raising money for men's health. This is no somber vigil or all-day walkathon. It's an act of raising awareness that is easily integrated into a man's everyday life. One that is happily tweeted, Instagrammed, and discussed around dinner tables, over cubes, and in locker rooms.
Movember has achieved exactly what it set out to do: get people talking. And for that, all seasonal-moustache touters should be proud.
By Joanna Berliner, Editor
So, what do you think? Tweet us at @ruelala with #inmyopinion and let us know.
Not a Member and like The (Style) Guide? You'll love Rue La La. Join now.


text:
- Home
- News
- Sports
- Opinion
- Obituaries
- Features
- Special Sections
- Classifieds
- Public Notices
Forgot Password? | Not a User? Sign up
Rain forced the annual Memorial Day ceremony on the courthouse lawn inside this year. During the event, local veterans were honored for their service in each of the branches of the armed forces.
Flags lined the streets in La Grange during the Monday holiday.
American Legion Post No. 39 laid flags on veterans' graves at Valley of Rest Cemetery on May 22.They placed a total of 510 flags – 496 flags on graves and 14 at the monument for the 14 veterans buried overseas. The monument lists those soldiers' names.
If you currently subscribe or have subscribed in the past to the Oldham Era, then simply find your account number on your mailing label and enter it below.
Click the question mark below to see where your account ID appears on your mailing label.
If you are new to the award winning Oldham Era and wish to get a subscription or simply gain access to our online content then please enter your ZIP code below and continue to setup your account.
|ZIP Code: