Atomic operations
[@NvidiaprogGuide] (see section [chap:CUDA]) are essential in
multithreaded programming, especially when different threads need to
read or write the same data location. Conventional multicore CPUs
generally use a test-and-set instruction to manage which thread
controls which data. CUDA has a much more extensive set of atomic
operations98
but, in a parallel environment they represent a real challenge
because they serialize the execution flow. In other words, incrementing
a single counter with atomicAdd()
means that the counter
has to be locked, thus forcing all threads to stop and wait in order to
individually perform the increment operation — one after the other;
it is the antithesis of parallel programming. The goal, when using this
kind of operation is to design low-wait algorithms,
s.t. the number of threads that must wait for the lock to be released
is kept to the minimum and, at the same time, maximixing the active
threads number.99
With CUDA, one can effectively perform a test-and-set using the
atomicInc()
instruction or use atomic operations as well, to
actually manipulate the data itself, without the need for a lock
variable.
Atomic functions have to be used with caution also due to another possible performance side-effect: when operating from global memory they are not cached. This means that every time an atomic operation is performed there must be a read from the global memory, and if the value needs to be modified, there must be a write to global memory too. This can take hundreds of clock cycles to accomplish. The CUDA architecture is set up to withstand extreme latency but, if too many threads are stalled, the computational throughput of the GPU will severely diminish.
Atomic functions were successfully employed in solving the problem of race conditions faced in section [sect:raceCondAvoiding]. They open the possibility of utilize the original (see section [sect:sciaraModelTau2]) lava distribution schema across the cells instead the creation and management of another substate. They allow a more direct and easy porting, because the responsibility of the computational coherence rely on the CUDA framework instead on the programmer. The implementation is such that during the distribution phase each substate is managed via atomic functions. An example in listing [code:atomicDistribution] shows how a cell distribute quantities to its 1-th neighbor (the same concept holds for the whole neighborhood).
int lungCOL=d_params[EN_LY];
float cache=d_outFlwPriv[getPrivateVarIdx(index,0,1)];
int idxNeigh=getNeigh1(index,lungCOL);
if (cache > 0){
//central cell lava flow subtraction
atomicAdd(&d_nSh[index],-cache);
//neighbor - lava flow
atomicAdd(&d_nSh[idxNeigh],+cache);
//neighbor - momentum along x-axis
atomicAdd(&d_nSpx[idxNeigh],cache*d_outFlwPriv[getPrivateVarIdx(index,1,1)]*COS_ALPHA_1);
//neighbor - momentum along y-axis
atomicAdd(&d_nSpy[idxNeigh],cache*d_outFlwPriv[getPrivateVarIdx(index,1,1)]*SIN_ALPHA_1);
//central cell temperature subtraction
atomicAdd(&d_nST[index],-cache*d_ST[index]);
//neighbor - temperature
atomicAdd(&d_nST[idxNeigh],cache*d_ST[index]);
...
}
Despite its simplicity, this approach does not allow the utilization (on the available hardware) of double precision buffers, because the framework does not expose any official100 support for atomic operations on double. It will be shown in section [sect:precisionConsid] that in SCIARA-fv3, double precision may be crucial for the correctness of final result. A different discussion is reserved for atomic operations on Kepler family GPUs that are more efficient than on Fermi GPUs insomuch they can often be processed at rates similar to global load operations 101.
Note that within this setting each substate value of each cell may be modified by a maximum number of 9 threads per step (the whole neighborhood itself) meaning that the global memory substate updates of a cell may stall not more that 9 threads, so it is possible to classify this approach as low-wait. In addition, in real case simulation it is very improbable that at each step all the active cells are interested by all the 9 outflowing flows, and this furtherly decreases the overall serialization rate.


A web application developer and designer, delivering frontend UI & backend systems software for scholarly communication, digital preservation and institutional repository services.


Start/restart the virtual device.
Stop the virtual device.
Dump network packets to file.
Stop dumping network packets.
'cdma ssource <ssource>' allows you to specify where to read the subscription from
'cdma ssource <ssource>' allows you to specify where to read the subscription from
nv: Read subscription from non-volatile RAM ruim: Read subscription from RUIM
Delete snapshot state.
Query virtual device name.
List available state snapshots.
Query virtual device status.
Dump network status.
Dump network status.
A vector with the download speed and upload speed (in bits/s), and the minimum and maximum latency (in ms).
List all code aliases for a given type.
List all type aliases.
List current phone calls.
Dump network status.
Dump network status.
A vector with the download speed and upload speed (in bits/s), and the minimum and maximum latency (in ms).
Display battery and charger state.
Display battery and charger state.
A vector with AC, status, health, present, and capacity in indices 0-4.
List current redirections.
List all sensors and their status.
List all sensors and their status.
A vector with the elements 'acceleration, magnetic-field, orientation, temperature, proximity
Get sensor value.
Change the state of an outbound call to 'active'.
Change the state of an outbound call to 'active'.
The phone number format with only digits, '#', and '+'.
Close waiting outbound call as busy.
Close waiting outbound call as busy.
The phone number format with only digits, '#', and '+'.
Create inbound phone call.
Create inbound phone call.
The phone number format with only digits, '#', and '+'.
Disconnect an inbound or outbound phone call.
Modify data connection state.
Modify data connection state.
Valid values for <state> are the following:
unregistered no network available home on local network, non-roaming roaming on roaming network searching searching networks denied emergency calls only off same as 'unregistered' on same as 'home'
Change the state of an outbound call to 'held'
Change the state of an outbound call to 'held'
The phone number format with only digits, '#', and '+'.
Sets the rssi and ber.
Sets the rssi and ber.
range is 0..31 and 99 for unknown
range is 0..7 percent and 99 for unknown
Return GSM status.
Return GSM status.
A Vector with the first element being the voice status and the second being the data status.
Modify voice connection state.
Modify voice connection state.
Valid values for <state> are the following:
unregistered no network available home on local network, non-roaming roaming on roaming network searching searching networks denied emergency calls only off same as 'unregistered' on same as 'home'
Load snapshot state.
Dump network packets to file.
Stop dumping network packets.
Set AC charging state.
Set battery capacity state.
Set battery health state.
Set battery present state.
Set battery status.
Set battery status.
unknown|charging|discharging|not-charging|full"
Add new redirection.
Add new redirection.
tcp|udp
Remove existing redirection.
Save snapshot state.
Simulate keystrokes from a given text.
Send a simple GPS fix.
Send a GPS NMEA sentence.
Send a series of events to the kernel.
Send a telnet command to an Android device and return the output.
Change network latency.
Change network speed.
Change network latency.
Change network speed.
Set sensor value.
'sms pdu <hexstring>' allows you to simulate a new inbound sms PDU (used internally when one emulator sends SMS messages to another instance).
'sms send <phonenumber> <message>' allows you to simulate a new inbound sms message.
Kill the emulator instance.
Change the window scale.


---
layout: post
title: Rails session.
date: 2018-04-22 13:03:24.000000000 +05:30
type: post
parent_id: '0'
published: true
password: ''
status: publish
categories: []
tags: []
authors:
- nithinr07
---
Why Rails ??
- First of all it is very fast to code a project in rails. So have a this knowledge with us will be a very big advantage during coding competitions and hackathons.
- It follows Convention over configuration which helps the programmer a lot during decision making.
- There are plenty of gems(libraries) available which makes the development lot easier. And as the community is huge these libraries are always kept uptodate
- As the rails user-base is increasing exponentially, the chances of this getting outdated is very slim.
Controllers
- Controller is the place where the logic of the program is written.
- It receives all the requests from the application.
- The received requests are processed here, and appropriate response is created
- It is also used for just updating the database with new data.
it will be more clear as you go through one example.
Models
- Models are nothing but your data bases.
- These are ruby classes where information are stored or retrieved.
Views
- Views contain the dynamic web pages that the users will be seeing. While Models and controllers are kept behind the curtains.
- These pages connect the users with the server in the backend
- They are written in a special format called Embedded Ruby(.erb)
The official documentation explains the work flow in the best possible way with examples
And Do learn about rails-scaffolding which generates the entire work that was done in the above tutorial in just one terminal command :)
Going through all these will give deeper insights.
Other Thoughts:
-
It is better to keep 3 terminals open
- for rails c (rails console, this can be used during testing for manipulating data in server side without touching the website)
- rails s (for rails server)
- rails routes
-
Migration helps us in maintaining a version control for our database. So having clean migration files will help a lot, as it is very easy to roll back to previous versions.
-
Difference between render and redirect:
Render function will generate the view to the browser, when render function is not called in the controller it generates the default view of the controller.
Redirect tells the browser to make a entire new request to a page.
It is not required to make new requests every time. So think before you use redirect function.
Special thanks to Biswesh for the session. Hope this helped.


Front End Developer
I am interested to learn how the computer works and interaction with the human beings.
I am also tech enthusiast. write down code in computer is my hobies,
but also sometimes make me dissapointed when the code doens't work,
but this is the challanges to solve unwork code is not easy.
logical thinking, patience, careful, and never quit all those needed to be a developer.


CSS Responsive Design
In this exercise you learn the basics of CSS responsive design
Exercise
Use the solution of the css-basic exercise CSS Basics Solution
- Create a responsive layout which break at a viewport widths of 750px according to the following screenshots
- The maximum width of the navigation bar if the viewport is above 750px should be 15em
- The text in the navigation should be aligned left if the viewport is above 750px
- If the users prints the document the navigation bar should be hidden and all backgrounds should be white
Template
Solution
Linkcss-responsive.solution1.html
Alternative Solution
Linkcss-responsive.solution2.html


Patanjali Kumar
01
Home
02
Resume
03
Skills
04
Projects
Patanjali Kumar
What i do
My Skills
Frameworks
Object-Oriented Programming
Functional Programming
Entity Mapping
Recommender Systems
Deep Learning
Web Scraping
Libraries | Tools
Jupyter Lab/Notebooks
Tensorflow
Pandas
Numpy
Matplotlib
Seaborn
Scikit-learn
GitHub
Agile | Kanban | Scrum
Postman ~ API testing
Languages
Python
Java
OCaml
Ruby
C | C++
SQL
Git
Linux Bash
HTML | CSS
Rust


--- layout: main ---
Use annotations to bind data to views without any view lookup. Sync all view data in one go and keep view states up to date with application state at all times. View holders are bulit in.
Witch is a light weight and performant view-data binding framework that helps building predictable UI:s.
Unlike the Data binding library that is part of jetpack, there are no bindings declared in the layout xml and there are no binding adapters.
Witch has less ceremony, is simpler to use and dictates no underlying architecture.
A binder (or whatever you may call it) is the core class you need to define in order to bind data to views. It's just a plain class with annotations declaring data and bindings. Below is a small example of a binder binding a user model to a text view:
Data is bound when a binder and a view (or an activity) is passed to Witch.bind().
The @Data-annotation is used to declare data properties. Only data properties can be used in bind methods. Each time a binder is passed to Witch.bind()
the data properties will evaluated. Only properties that has changed since last bind will be bound.
In the above example, the entire user model is declared a data property despite only the user name is bound to a view.
This might be OK in some cases, but if the user model is frequently updated, the name will be repeatedly bound without being changed.
Since the @Data-annotation can be used on methods, we can create a data property just for the user name. This way the name is only bound
when actually changed.
The @Bind-annotation is used to declare bind methods. This is how data gets bound to a view. The view is looked up (once) with the id defined in the annotation. Data passed to the bind method is mapped using type and name of any data property in the same class.
If a binding is simply setting data on a view the @Data and @Bind-annotation can be merged to a @BindData-annotation. The annotation must define a view type and what property to set.
The @Setup-annotation is used to declare bind methods that should only run once. Setup methods will always run before any bind methods.
The @BindNull-annotation enables null values to be used in bind methods. By default, null values are ignored.
Witch will create view holders for all annotated views. This eliminates the need for creating additional
view holders for adapter views.
WitchRecyclerViewAdapter makes it easy implement data bindings for a recycler view.
Binders must extend WitchRecyclerViewAdapter.Binder. In this case, the PostBinder will handle binding of all items of type Post in the adapters data set. For each position, the binder will be updated with the corresponding data item that will be accassible through the magical property item and should only be reference from within a bind method.
Multiple data types are supported by simply providing multiple binders to the adapter.
Data is bound in same order as the bind methods are defined.
From a performance perspective, it is important that views are not updated unnecessarily.
Updating views can cause chains of measure and layout passes and should be avoided if possible.
Witch is designed to only bind data that has changed since last bind pass. Besides positive effect on performance,
this alows for things like animations to be executed from bind methods with no risk of running when data has not changed.
This behaviour can be altered by using the @BindWhen annotation.
The default strategy for all values is BindWhen.NOT_EQUALS described below.
Enable logging to get readable representations of all targets when bound.


Disclaimer:The opinions expressed in this archive do not necessarily express the views of the host site (The EnviroLink Network, The Federation of American Scientists). All material has been compiled from publicly available sources. This information is provided only in the interest of increasing public awareness of the physics and effects of nuclear weapons, and to provide a convenient accessible reference for understanding nuclear weapons related public policy issues. |


Log in to your account
Don't have an account?
Sign up now
Email
Password
Forgot your password?
Log In


Home
About
Mojo Bar
Havana Club
Conrad
Things to do
Spend all your money :)
Contact
Suvarnabhumi Airport
Place to be
Login Here
of modern page


PMCMR: Calculate Pairwise Multiple Comparisons of Mean Rank Sums
Note, that the 'PMCMR' package is superseded
by the novel 'PMCMRplus' package. The 'PMCMRplus'
package contains all functions from
'PMCMR' and many more parametric and non-parametric
multiple comparison procedures, one-factorial trend
tests, as well as improved method functions,
such as print, summary and plot.
The 'PMCMR' package is no longer maintained,
but kept for compatibility of reverse depending
packages for some time.
Downloads:
Reverse dependencies:
| Reverse imports: |
jmv |
| Reverse suggests: |
mlr |
Linking:
Please use the canonical form
https://CRAN.R-project.org/package=PMCMR
to link to this page.


module Tag:sig
..end
type'a
t ='a Value.tag
register ~name ~uuid (module T)
creates a new variant
constructor, that accepts values of type T.t
. Module T
should implement Binable.S
and Sexpable.S
interfaces,
provide compare
and pretty-printing pp
functions. This
functions will be used to print, compare and serialize
values.
uuid
and name
parameters must be string literals, i.e.,
they must be known at compile time. This is to prevent the
abuse of type system.
The returned value of type T.t tag
is a special key that
can be used with create
and get
functions to pack and
unpack values of type T.t
into value
.
val register : name:Value.literal ->
uuid:Value.literal ->
(module Bap.Std.Value.S with type t = 'a) -> 'a Value.tag
val name : 'a t -> string
name cons
returns a name of a constructor.val same : 'a t -> 'b t -> bool
val same_witness : 'a t ->
'b t -> ('a, 'b) Type_equal.t option
val same_witness_exn : 'a t ->
'b t -> ('a, 'b) Type_equal.t


Updated CollectionGen for VS.NET 2002 & 2003
Here. I've updated CollectionGen with code to support both VS.NET 2002 & 2003. It has no dependencies on any VS.NET design-time DLLs, so one binary works for both versions. If you're building custom tools, this should form a good base to support both environments.


Canonical XML Implementation v0.5
Author
Christian Geuer-Pollmann<EMAIL_ADDRESS>University
of Siegen
Institute for Data Communications Systems
Needs the following packages
Packages
- {@link org.apache.xml.security.algorithms} contains algorithm factories
- {@link org.apache.xml.security.c14n} contains Canonicalization related material and algorithms
- {@link org.apache.xml.security.exceptions} contains all exceptions used by this library
- {@link org.apache.xml.security.keys} contains key related material
- {@link org.apache.xml.security.samples} contains some sample applications and non-standard transforms
- {@link org.apache.xml.security.signature} contains the XML Signature specific classes
- {@link org.apache.xml.security.transforms} XML Signature transformations
- {@link org.apache.xml.security.utils} contains all utility classes
- {@link org.apache.xml.security.test} JUnit test cases
- {@link org.apache.xml.security.temp} is the playground for messing around
Features
Currently, the examples 3.1 - 3.6 work as expected. For example "3.4
Character Modifications and Character References", the parser must switched to
validating mode to make the ID and NMTOKENS normalization.


cookie stand
we are open from 6:00AM untill 7:00PM
locations with addresses :
seattle : amman
Tokyo : irbd
Dubai : salt
paris : ajloun
lima : zarqa'a
sales Salmon


Inventory Management
Home
Team
Login
Created By
Jay Ganatra
Ankit Gala
Hrishikesh Bharadwaj
Your browser does not support the canvas element.


|
MatrixEngine
|
A visable entity. More...
#include <object.h>
Public Member Functions | |
| entity (const int &start_x, const int &start_y, char p_icon, const float &speed_x, const float &speed_y, const bool &gravity, const bool &bounce, const bool &solid) | |
| Constructs a entity. More... | |
| bool | get_stand () |
| void | set_stand (bool new_stand) |
| bool | get_solid () |
| returns solid More... | |
| char | get_icon () |
| returns icon More... | |
| float | get_speed_x () |
| returns x speed More... | |
| void | set_speed_x (float new_speed) |
| sets x speed More... | |
| float | get_speed_y () |
| returns yspeed More... | |
| void | set_speed_y (float new_speed) |
| sets y speed More... | |
| bool | get_gravity () |
| returns gravity More... | |
| bool | get_bounce () |
| returns bounce More... | |
| Public Member Functions inherited from object | |
| object (const int &start_x, const int &start_y) | |
| virtual int | get_x () |
| returns x More... | |
| virtual int | get_y () |
| returns y More... | |
| virtual void | set_x (int u_x) |
| sets x More... | |
| virtual void | set_y (int u_y) |
| sets y More... | |
| void | set_pos (int x, int y) |
| Set position to given coordinates. More... | |
| void | move_up () |
| Subtracts one from x. More... | |
| void | move_down () |
| Adds Sone from x. More... | |
| void | move_left () |
| Subtracts one from y. More... | |
| void | move_right () |
| Adds one from y. More... | |
Public Attributes | |
| unsigned int | score = 0 |
Protected Attributes | |
| char | icon |
| float | speed_x |
| float | speed_y |
| bool | gravity |
| bool | bounce |
| bool | stand = 0 |
| int | health = 100 |
| float | strength = 1 |
| float | weight = 1 |
| bool | solid |
| Protected Attributes inherited from object | |
| xy | posXY |
| position of object More... | |
A visable entity.
An entity that has an icon, a speed and optionally gravity and other physics.
|
inline |
Constructs a entity.
This constructor construct an entity
|
inline |
returns bounce
This function returns if the object can bounce
|
inline |
returns gravity
This function returns if this entity can be affected by gravity.
|
inline |
returns icon
This function returns entity's icon.
|
inline |
returns solid
returns if the object is solid
|
inline |
returns x speed
This function returns the x speed of object.
|
inline |
returns yspeed
returns entity's float variabel named speed_y.
|
inline |
sets x speed
This function sets entity's x speed to given speed.
|
inline |
sets y speed
This function sets entity's y speed to given speed.


Non-fullscreen windows can be created in one of four styles: default, dialog, tool or borderless. Examples of the appearances of each of these styles under Windows XP and Mac OS X 10.4 are shown below.
Style Windows XP Mac OS X WINDOW_STYLE_DEFAULT WINDOW_STYLE_DIALOG WINDOW_STYLE_TOOL
Non-resizable variants of these window styles may appear slightly different (for example, the maximize button will either be disabled or absent).
Besides the change in appearance, the window styles affect how the window behaves. For example, tool windows do not usually appear in the task bar and cannot receive keyboard focus. Dialog windows cannot be minimized. Selecting the appropriate window style for your windows means your application will behave correctly for the platform on which it is running, however that behaviour may not be consistent across Windows, Linux and Mac OS X.
The appearance and behaviour of windows in Linux will vary greatly depending on the distribution, window manager and user preferences.
Borderless windows (WINDOW_STYLE_BORDERLESS) are not decorated by the operating system at all, and have no way to be resized or moved around the desktop. These are useful for implementing splash screens or custom window borders.
You can specify the style of the window in the Window constructor. Once created, the window style cannot be altered:
window = pyglet.window.Window(style=window.Window.WINDOW_STYLE_DIALOG)
The window's caption appears in its title bar and task bar icon (on Windows and some Linux window managers). You can set the caption during window creation or at any later time using the set_caption method:
window = pyglet.window.Window(caption='Initial caption') window.set_caption('A different caption')
The window icon appears in the title bar and task bar icon on Windows and Linux, and in the dock icon on Mac OS X. Dialog and tool windows do not necessarily show their icon.
Windows, Mac OS X and the Linux window managers each have their own preferred icon sizes:
- Windows XP
- A 16x16 icon for the title bar and task bar.
- A 32x32 icon for the Alt+Tab switcher.
- Mac OS X
- Any number of icons of resolutions 16x16, 24x24, 32x32, 48x48, 72x72 and 128x128. The actual image displayed will be interpolated to the correct size from those provided.
- Linux
- No constraints, however most window managers will use a 16x16 and a 32x32 icon in the same way as Windows XP.
The Window.set_icon method allows you to set any number of images as the icon. pyglet will select the most appropriate ones to use and apply them to the window. If an alternate size is required but not provided, pyglet will scale the image to the correct size using a simple interpolation algorithm.
The following example provides both a 16x16 and a 32x32 image as the window icon:
window = pyglet.window.Window() icon1 = pyglet.image.load('16x16.png') icon2 = pyglet.image.load('32x32.png') window.set_icon(icon1, icon2)
You can use images in any format supported by pyglet, however it is recommended to use a format that supports alpha transparency such as PNG. Windows .ico files are supported only on Windows, so their use is discouraged. Mac OS X .icons files are not supported at all.
Note that the icon that you set at runtime need not have anything to do with the application icon, which must be encoded specially in the application binary (see Self-contained executables).


Education
DevBootcamp - 2015
UC Berkeley B.A. Architecture - 2011
Experience
- Assist on 5D BIM(Building information modeling), project renderings, design drawings, and furniture procurement for multi-million Veterans Affairs OPC projects and MOB projects
- Act as project team manager for multiple LEED Online projects. Manage documents and coordinate project issues between client and disciplines. Facilitate LEED green building certication process.
- Provide software training and project guidance to new junior staffs at office
Project Designer at MEI Architects - 1 year 8 months
- Prepare project bidding package for oversea projects and competitions
- Assist on project drawings and 3D modeling for local residential projects
Designer at Q-Architecture - 6 months
Software
Beginner: Html & CSS | Javascript | Ruby | Indesign | 3ds Max
Intermediate: AutoCAD | Revit | Photoshop | Illustrator | Mental Ray | V-Ray | MS Office
Advanced: Sketchup
Language
English | Mandarin | Cantonese


--- layout: posts title: Bordeaux image: bordeaux imagecaption: Harbour at Bordeaux, 1871 imageby: Édouard Manet date: 2016-03-04 tags: wset3 category: grape permalink: /grape/bordeaux/index.html published: true excerpt_separator: ---
This article is my study notes on Bordeaux for the WSET level3 certification.
The region is broken into two major areas for top-quality, the Left Bank, and the Right Bank.
The warming ocean current extends the growing season: spring frosts are rare and ripening well into October. The Atlantic also brings high levels of rainfall and humidity, which can disrupt flowering and fruit set, promote rot and dilute flavours. Vintage variation is an important consideration, top producers reject unhealthy and unripe grapes.
Thirteen varieties are permitted, but three black grapes and two white predominate.
Cabernet Sauvignon has thick skins, small berries resulting in a powerful, dry red wine. It is the main variety in the Left Bank, and a blending variety on the Right Bank. Buds and ripens 1 to 2 weeks after Merlot. Primary characters of blackcurrant, black cherry, secondary of cedar, smoke vanilla, coffee, and with maturity takes on vegetal, and tobacco.
Merlot is the most widely used variety where it serves as the primary grape in the Right Bank, and as a blending variety on the Left Bank, giving soften tannin structures and ripe fruits. It has thinner skins and buds/ripens 1 to 2 weeks eariler, has higher sugar, and lower malic acid than Cabernet Sauvignon. In has red fruit character, strawberry, red berry, plum, some herbal (mint), vanilla and coffee from oak, and develops cedar and tobacco with age.
Petit Verdot has far smaller plantings than Cabernet Sauvignon, Cabernet Franc, and Merlot . It fully ripens only in very hot years, giving deep color, tannins. It plays a minor role in the blend, adding color, tannin, and spicy notes.
Dry white made mostly from **Sauvignon Blanc**
Semillon is the dominate white variety used in botrytised grapes. Produces full-bodied grapes with honey. Also blended into Sauvignon Blanc in small percentage adding body and softening acidity. Luscious white made mostly from **Semillon**
The 1855 classification is an official list of the best red grapes of the Médoc and Graves and the best white grapes of Sauternes. Chateaux (estate or grapery) within this classification are Cru Classé divided into five ranks. Further classification Cru Bourgeois later introduced for other chateaux, awarded to specific vintages
The wine is clear medium ruby.
The wine is clean with medium - intensity, aromas of red cherries, cranberries, red plum, bell pepper, black currant. The wine is developing.
The wine is dry, medium + acidity, medium + tannin, medium alcohol, medium - body, and bell pepper, black currant, black cherry, red plum, less ripe than nose. The wine has medium intensity and medium finish.
Good.
Drink now, not suitable for ageing.
A group of lesser-known red grape appellations, Blaye, Cadillac, Castillon, and Francs. Cotes de Bourg is similar style, but chose not to join the AOC
Merlot based for early drinking providing excellent value for money.
Bordeaux Supérieur has stricter rules than Bordeaux AOC, requires higher level of alcohol, aged for at least 12 months, planted more densely than Bordeaux AOC and therefore harder for the plants to survive creating stronger deeper roots. Blends, with the reds being predominantly Cabernet Sauvignon and Merlot with smaller amounts of Cab Franc, Petit Verdot, Malbec and even some Carmenere. Early drinking medium bodied grapes with ripe red and black fruit.
Significant amounts of Merlot. Cabernet Sauvignon found in the outcrops of gravel. Only dry white grapes of average quality from Sauvignon Blanc in an unoaked style labeled Appellation Entre-Deux-Mers Controlée. Red grapes are sold as Bordeaux AOC or Bordeaux Supérieur AOC
Médoc ispredominantly clay, but with outcrops of gravel. These grapes tend to have a higher portion of Merlot than Haut-Médoc AOC, based on cool clay soil Cabernet Sauvignon found in the outcrops of gravel.
Chateaux within the 1855 classification are Cru Classé divided into five ranks. Top rank consists of Châteaux Lafite Rothschild, Latour, Margaux, Mouton Rothschild
These grapes tend to be more highly rated than Médoc AOC. Stone/gravel, conditions are far superior to the rest of the Médoc.
Cabernet Sauvignon dominates Haut Médoc, where stone/gravel raises temperature. These wines have a high percentage of Cabernet Sauvignon. These grapes generally have flavours and aromas of blackcurrant, and cedar. These wines can have grippy tannins when young, and often have a long ageing potential.
The wine is clear deep garnet.
The wine is clean with medium + intensity, aromas of dried cranberries, black berry, black currant, mint, cedar, toast, oak, mushroom. The wine is developing.
The wine is dry, medium + acidity, high tannin, high alcohol, medium + body, and dried cranberries, black berry, black currant, mint, cedar, toast, oak, mushroom. The wine has pronounced intensity and a long finish.
Very good.
Drink now, suitable for further ageing.
Saint Estèphe is located at the northernmost of the four important Haut Médoc communes, the lesser known commune of the top four. It mainly produces Cabernet Sauvignon with powerful tannin structure, age-worthy
Château Lafite Rothschild, Les Grands Crus classés en 1855, Château Latour, Les Grands Crus classés en 1855, Château Mouton Rothschild, Les Grands Crus classés en 1855, Powerful, full-flavored, and long-lived
The wine is clear deep garnet.
 The wine is developing.
The wine is dry, medium + acidity, high tannin, medium alcohol, medium + body, and black berries, black plum, black cherry, toast, cedar, tobacco, mushroom. The wine has pronounced intensity and a long finish.
Outstanding.
Drink now, suitable for further ageing. (still lots of primary fruit will improve with age)
Saint-Julien is located just south of Pauillac and Saint Julien, the smallest of the top four. Cabernet Sauvignon with powerful tannin structure, age-worthy.
located at the southernmost of the four important Haut Médoc communes, Cabernet Sauvignon, Château Margaux, Les Grands Crus classés en 1855. Very elegant, smooth and soft tannins, intense aroma
Gravel soil, ideal terror for top-quality red and white grapes. Cabernet Sauvignon and Sauvignon Blanc.
stone/gravel. Cabernet Sauvignon dominates, where stone/gravel raises temperature. Merlot producers blend more Merlot into their grapes, producing a softer tannin structure. Haut-Brion, Les Grands Crus classés en 1855
north and west of town gravel/limestone soil, warm and well drained. South and east with clay limestone soil.The largest top-quality commune in Bordeaux. Organized into it’s own classification system (Saint Emilion, Saint Emilion Satellites, Grand Cru)
Merlot is widely planted, due to cooler clay soil, complex red berry fruit and plum, developing tobacco and cedar. Softer grapes drinkable earilier.
Cabernet Franc is used widely, produces less body and tannin than Cabernet Sauvignon. Herbaceous flavours when unripe and when ripe vibrant fruit and floral notes. It prefers well drained soils
The smallest of the top-quality communes in Bordeaux. Limited supply keeps prices high.
Merlot is widely planted, due to cooler clay soil. Richer with a spicier blackberry fruit character. Softer tannins than the Left Bank.
Cabernet Franc used to blend
Cabernet Sauvignon used to blend.
The wine is clear deep garnet.
The wine is clean with medium + intensity, aromas of black cherries, red cherries, black and red plum, cedar, toast, chocolate, tobacco. The wine is developing.
The wine is dry, medium acidity, medium + tannin, medium + alcohol, full body, and black cherries, red cherries, black and red plum, cedar, toast, chocolate, tobacco. The wine has medium + intensity and a long finish.
Very good, lacks some complexity and some intensity.
Drink now, suitable for further ageing.
Yquem, Les Grands Crus classés en 1855


Toggle navigation
Dlapak
Advertise
Signup
Pages
My Ads
Create Ads
My Profile
Remember me
Forgot password?
Find an Awesome Things Here
Find all things you need on DLapak. We give you a simple way.
All Location
New York
Washington
California
Car
234,567
Motorcycle
25,366
Property
252,546
Fashion
52,546
Gadget
215,546
Sport
415,546
Industry
15,546
Job
152,546
Featured
Featured Ads
Lenovo A326 Black 4GB RAM
Today 10.35 am
Electronics
,
Smartphone
Manchester
New
Featured Ads
Samsung Tab 3 V 116
Today 10.35 am
Electronics
,
Smartphone
Manchester
New
Sony Experia Z2 LTE
Today 10.35 am
Electronics
,
Smartphone
Manchester
New
Featured Ads
Lenovo A326 Black 4GB RAM
Today 10.35 am
Electronics
,
Smartphone
Manchester
New
Featured Ads
Lenovo A326 Black 4GB RAM
Today 10.35 am
Electronics
,
Smartphone
Manchester
New
Quick Signup
I Agree with Term and Conditions
Sign Up
Trends
Smartphone
(2,342)
Watch & Jewelry
(2,342)
Clothes
(2,342)
Shoes
(2,342)
Music
(2,342)
Furniture
(2,342)
Photography
(242)
Web Development
(2,342)
7803
Items
427
Sellers
639
Locations
1548
Members


HOME
Dashboard
Searching History
View History
User Managements
Pinned Question
Pinned Question
QuestionID
Title
Pin Text
Site
Date Time
OwnerID
QuestionID
Title
Pin Text
Site
Date Time
OwnerID
Confirm deleting
×
Are you sure to delete this record ?


A tag is a type of the form
tag<T>
for some arbitrary
T
.
In the context of Boost.Flyweight, tags are syntactic artifacts used
to differentiate instantiations of the class template
flyweight
which would
otherwise be identical. Tagging a flyweight
instantiation with
a tag type local to a given context ensures that the global resources
of that instantiation (for instance, the associated
factory class) will not be unintentionally
shared by other areas of the program.
一个标签是tag<T>
这种格式的类型，其中T
可以是任意类型。在Boost.Flyweight的上下文里，标签是用来人为的区分相同的flyweight
类模板实例的语法标记。用一个临近给定上下文的tag来标记一个flyweight
的实例，确保那个实例的全局资源（例如，相关的工厂类）不会在无意中被程序的其它部分所共享。
"boost/flyweight/tag.hpp"
synopsis "boost/flyweight/tag.hpp"
大意
namespace boost{ namespace flyweights{ template<typename T> struct tag; } // namespace boost::flyweights } // namespace boost
tag 类模板 tag
For any type T
, tag<T>
is a suitable
tag for use in instantiations of
flyweight
.
对任何类型T，
tag<T>
都是一个可以用在flyweight
实例中的合适的标签。
Revised August 11th 2008
© Copyright 2006-2008 Joaquín M López Muñoz. Distributed under the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)


The tuxedo package is typically for men only and includes tuxedo jacket, tuxedo pants and shirt, bow tie, cummerbund, cuff links and dress shoes. Please be sure to bring your own socks. For the most accurate measurement, have someone help you with a tape measure.
PLEASE NOTE: If you plan to wear your own tuxedo to the gala, you must inform terry_lincoln@agilent.com


| PostgreSQL 9.0.10 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Appendix E. Release Notes | Next |
Release Date: 2010-09-20
This release of PostgreSQL adds features that have been requested for years, such as easy-to-use replication, a mass permission-changing facility, and anonymous code blocks. While past major releases have been conservative in their scope, this release shows a bold new desire to provide facilities that new and existing users of PostgreSQL will embrace. This has all been done with few incompatibilities. Major enhancements include:
Built-in replication based on log shipping. This advance consists of two features: Streaming Replication, allowing continuous archive (WAL) files to be streamed over a network connection to a standby server, and Hot Standby, allowing continuous archive standby servers to execute read-only queries. The net effect is to support a single master with multiple read-only slave servers.
Easier database object permissions management. GRANT/REVOKE IN SCHEMA supports mass permissions changes on existing objects, while ALTER DEFAULT PRIVILEGES allows control of privileges for objects created in the future. Large objects (BLOBs) now support permissions management as well.
Broadly enhanced stored procedure support. The DO statement supports ad-hoc or "anonymous" code blocks. Functions can now be called using named parameters. PL/pgSQL is now installed by default, and PL/Perl and PL/Python have been enhanced in several ways, including support for Python3.
Full support for 64-bit Windows.
More advanced reporting queries, including additional windowing options (PRECEDING and FOLLOWING) and the ability to control the order in which values are fed to aggregate functions.
New trigger features, including SQL-standard-compliant per-column triggers and conditional trigger execution.
Deferrable unique constraints. Mass updates to unique keys are now possible without trickery.
Exclusion constraints. These provide a generalized version of unique constraints, allowing enforcement of complex conditions.
New and enhanced security features, including RADIUS authentication, LDAP authentication improvements, and a new contrib module passwordcheck for testing password strength.
New high-performance implementation of the LISTEN/NOTIFY feature. Pending events are now stored in a memory-based queue rather than a table. Also, a "payload" string can be sent with each event, rather than transmitting just an event name as before.
New implementation of VACUUM FULL. This command now rewrites the entire table and indexes, rather than moving individual rows to compact space. It is substantially faster in most cases, and no longer results in index bloat.
New contrib module pg_upgrade to support in-place upgrades from 8.3 or 8.4 to 9.0.
Multiple performance enhancements for specific types of queries, including elimination of unnecessary joins. This helps optimize some automatically-generated queries, such as those produced by object-relational mappers (ORMs).
EXPLAIN enhancements. The output is now available in JSON, XML, or YAML format, and includes buffer utilization and other data not previously available.
hstore improvements, including new functions and greater data capacity.
The above items are explained in more detail in the sections below.
A dump/restore using pg_dump, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.
Version 9.0 contains a number of changes that selectively break backwards compatibility in order to support new features and code quality improvements. In particular, users who make extensive use of PL/pgSQL, Point-In-Time Recovery (PITR), or Warm Standby should test their applications because of slight user-visible changes in those areas. Observe the following incompatibilities:
Remove server parameter add_missing_from, which was defaulted to off for many years (Tom Lane)
Remove server parameter regex_flavor, which was defaulted to advanced for many years (Tom Lane)
archive_mode now only affects archive_command; a new setting, wal_level, affects the contents of the write-ahead log (Heikki Linnakangas)
log_temp_files now uses default file size units of kilobytes (Robert Haas)
When querying a parent table, do not do any separate permission checks on child tables scanned as part of the query (Peter Eisentraut)
The SQL standard specifies this behavior, and it is also much more convenient in practice than the former behavior of checking permissions on each child as well as the parent.
bytea output now appears in hex format by default (Peter Eisentraut)
The server parameter bytea_output can be used to select the traditional output format if needed for compatibility.
Array input now considers only plain ASCII whitespace characters to be potentially ignorable; it will never ignore non-ASCII characters, even if they are whitespace according to some locales (Tom Lane)
This avoids some corner cases where array values could be interpreted differently depending on the server's locale settings.
Improve standards compliance of SIMILAR TO
patterns and SQL-style substring()
patterns (Tom Lane)
This includes treating ? and {...} as
pattern metacharacters, while they were simple literal characters
before; that corresponds to new features added in SQL:2008.
Also, ^ and $ are now treated as simple
literal characters; formerly they were treated as metacharacters,
as if the pattern were following POSIX rather than SQL rules.
Also, in SQL-standard substring()
, use of parentheses
for nesting no longer interferes with capturing of a substring.
Also, processing of bracket expressions (character classes) is
now more standards-compliant.
Reject negative length values in 3-parameter substring()
for bit strings, per the SQL standard (Tom Lane)
Make date_trunc
truncate rather than round when reducing
precision of fractional seconds (Tom Lane)
The code always acted this way for integer-based dates/times. Now float-based dates/times behave similarly.
Tighten enforcement of column name consistency during RENAME when a child table inherits the same column from multiple unrelated parents (KaiGai Kohei)
No longer automatically rename indexes and index columns when the underlying table columns are renamed (Tom Lane)
Administrators can still rename such indexes and columns manually. This change will require an update of the JDBC driver, and possibly other drivers, so that unique indexes are correctly recognized after a rename.
CREATE OR REPLACE FUNCTION can no longer change the declared names of function parameters (Pavel Stehule)
In order to avoid creating ambiguity in named-parameter calls, it is no longer allowed to change the aliases for input parameters in the declaration of an existing function (although names can still be assigned to previously unnamed parameters). You now have to DROP and recreate the function to do that.
PL/pgSQL now throws an error if a variable name conflicts with a column name used in a query (Tom Lane)
The former behavior was to bind ambiguous names to PL/pgSQL variables in preference to query columns, which often resulted in surprising misbehavior. Throwing an error allows easy detection of ambiguous situations. Although it's recommended that functions encountering this type of error be modified to remove the conflict, the old behavior can be restored if necessary via the configuration parameter plpgsql.variable_conflict, or via the per-function option #variable_conflict.
PL/pgSQL no longer allows variable names that match certain SQL reserved words (Tom Lane)
This is a consequence of aligning the PL/pgSQL parser to match the core SQL parser more closely. If necessary, variable names can be double-quoted to avoid this restriction.
PL/pgSQL now requires columns of composite results to match the expected type modifier as well as base type (Pavel Stehule, Tom Lane)
For example, if a column of the result type is declared as NUMERIC(30,2), it is no longer acceptable to return a NUMERIC of some other precision in that column. Previous versions neglected to check the type modifier and would thus allow result rows that didn't actually conform to the declared restrictions.
PL/pgSQL now treats selection into composite fields more consistently (Tom Lane)
Formerly, a statement like SELECT ... INTO rec.fld FROM ... was treated as a scalar assignment even if the record field fld was of composite type. Now it is treated as a record assignment, the same as when the INTO target is a regular variable of composite type. So the values to be assigned to the field's subfields should be written as separate columns of the SELECT list, not as a ROW(...) construct as in previous versions.
If you need to do this in a way that will work in both 9.0 and previous releases, you can write something like rec.fld := ROW(...) FROM ....
Remove PL/pgSQL's RENAME declaration (Tom Lane)
Instead of RENAME, use ALIAS, which can now create an alias for any variable, not only dollar sign parameter names (such as $1) as before.
Deprecate use of => as an operator name (Robert Haas)
Future versions of PostgreSQL will probably reject this operator name entirely, in order to support the SQL-standard notation for named function parameters. For the moment, it is still allowed, but a warning is emitted when such an operator is defined.
Remove support for platforms that don't have a working 64-bit integer data type (Tom Lane)
It is believed all still-supported platforms have working 64-bit integer data types.
Version 9.0 has an unprecedented number of new major features, and over 200 enhancements, improvements, new commands, new functions, and other changes.
PostgreSQL's existing standby-server capability has been expanded both to support read-only queries on standby servers and to greatly reduce the lag between master and standby servers. For many users, this will be a useful and low-administration form of replication, either for high availability or for horizontal scalability.
Allow a standby server to accept read-only queries (Simon Riggs, Heikki Linnakangas)
This feature is called Hot Standby. There are new postgresql.conf and recovery.conf settings to control this feature, as well as extensive documentation.
Allow write-ahead log (WAL) data to be streamed to a standby server (Fujii Masao, Heikki Linnakangas)
This feature is called Streaming Replication. Previously WAL data could be sent to standby servers only in units of entire WAL files (normally 16 megabytes each). Streaming Replication eliminates this inefficiency and allows updates on the master to be propagated to standby servers with very little delay. There are new postgresql.conf and recovery.conf settings to control this feature, as well as extensive documentation.
Add pg_last_xlog_receive_location()
and pg_last_xlog_replay_location()
, which
can be used to monitor standby server WAL
activity (Simon Riggs, Fujii Masao, Heikki Linnakangas)
Allow per-tablespace values to be set for sequential and random page cost estimates (seq_page_cost/random_page_cost) via ALTER TABLESPACE ... SET/RESET (Robert Haas)
Improve performance and reliability of EvalPlanQual rechecks in join queries (Tom Lane)
UPDATE, DELETE, and SELECT FOR UPDATE/SHARE queries that involve joins will now behave much better when encountering freshly-updated rows.
Improve performance of TRUNCATE when the table was created or truncated earlier in the same transaction (Tom Lane)
Improve performance of finding inheritance child tables (Tom Lane)
Remove unnecessary outer joins (Robert Haas)
Outer joins where the inner side is unique and not referenced above the join are unnecessary and are therefore now removed. This will accelerate many automatically generated queries, such as those created by object-relational mappers (ORMs).
Allow IS NOT NULL restrictions to use indexes (Tom Lane)
This is particularly useful for finding
MAX()
/MIN()
values in indexes that
contain many null values.
Improve the optimizer's choices about when to use materialize nodes, and when to use sorting versus hashing for DISTINCT (Tom Lane)
Improve the optimizer's equivalence detection for expressions involving boolean <> operators (Tom Lane)
Use the same random seed every time GEQO plans a query (Andres Freund)
While the Genetic Query Optimizer (GEQO) still selects random plans, it now always selects the same random plans for identical queries, thus giving more consistent performance. You can modify geqo_seed to experiment with alternative plans.
Improve GEQO plan selection (Tom Lane)
This avoids the rare error "failed to make a valid plan", and should also improve planning speed.
Improve ANALYZE to support inheritance-tree statistics (Tom Lane)
This is particularly useful for partitioned tables. However, autovacuum does not yet automatically re-analyze parent tables when child tables change.
Improve autovacuum's detection of when re-analyze is necessary (Tom Lane)
Improve optimizer's estimation for greater/less-than comparisons (Tom Lane)
When looking up statistics for greater/less-than comparisons, if the comparison value is in the first or last histogram bucket, use an index (if available) to fetch the current actual column minimum or maximum. This greatly improves the accuracy of estimates for comparison values near the ends of the data range, particularly if the range is constantly changing due to addition of new data.
Allow setting of number-of-distinct-values statistics using ALTER TABLE (Robert Haas)
This allows users to override the estimated number or percentage of distinct values for a column. This statistic is normally computed by ANALYZE, but the estimate can be poor, especially on tables with very large numbers of rows.
Add support for RADIUS (Remote Authentication Dial In User Service) authentication (Magnus Hagander)
Allow LDAP (Lightweight Directory Access Protocol) authentication to operate in "search/bind" mode (Robert Fleming, Magnus Hagander)
This allows the user to be looked up first, then the system uses the DN (Distinguished Name) returned for that user.
Add samehost and samenet designations to pg_hba.conf (Stef Walter)
These match the server's IP address and subnet address respectively.
Pass trusted SSL root certificate names to the client so the client can return an appropriate client certificate (Craig Ringer)
Add the ability for clients to set an application name, which is displayed in pg_stat_activity (Dave Page)
This allows administrators to characterize database traffic and troubleshoot problems by source application.
Add a SQLSTATE option (%e) to log_line_prefix (Guillaume Smet)
This allows users to compile statistics on errors and messages by error code number.
Write to the Windows event log in UTF16 encoding (Itagaki Takahiro)
Now there is true multilingual support for PostgreSQL log messages on Windows.
Add pg_stat_reset_shared('bgwriter')
to reset the cluster-wide shared statistics for the
background writer (Greg Smith)
Add pg_stat_reset_single_table_counters()
and pg_stat_reset_single_function_counters()
to allow resetting the statistics counters for individual
tables and functions (Magnus Hagander)
Allow setting of configuration parameters based on database/role combinations (Alvaro Herrera)
Previously only per-database and per-role settings were possible, not combinations. All role and database settings are now stored in the new pg_db_role_setting system catalog. A new psql command \drds shows these settings. The legacy system views pg_roles, pg_shadow, and pg_user do not show combination settings, and therefore no longer completely represent the configuration for a user or database.
Add server parameter bonjour, which controls whether a Bonjour-enabled server advertises itself via Bonjour (Tom Lane)
The default is off, meaning it does not advertise. This allows packagers to distribute Bonjour-enabled builds without worrying that individual users might not want the feature.
Add server parameter enable_material, which controls the use of materialize nodes in the optimizer (Robert Haas)
The default is on. When off, the optimizer will not add materialize nodes purely for performance reasons, though they will still be used when necessary for correctness.
Change server parameter log_temp_files to use default file size units of kilobytes (Robert Haas)
Previously this setting was interpreted in bytes if no units were specified.
Log changes of parameter values when postgresql.conf is reloaded (Peter Eisentraut)
This lets administrators and security staff audit changes of database settings, and is also very convenient for checking the effects of postgresql.conf edits.
Properly enforce superuser permissions for custom server parameters (Tom Lane)
Non-superusers can no longer issue ALTER ROLE/DATABASE SET for parameters that are not currently known to the server. This allows the server to correctly check that superuser-only parameters are only set by superusers. Previously, the SET would be allowed and then ignored at session start, making superuser-only custom parameters much less useful than they should be.
Perform SELECT FOR UPDATE/SHARE processing after applying LIMIT, so the number of rows returned is always predictable (Tom Lane)
Previously, changes made by concurrent transactions could cause a SELECT FOR UPDATE to unexpectedly return fewer rows than specified by its LIMIT. FOR UPDATE in combination with ORDER BY can still produce surprising results, but that can be corrected by placing FOR UPDATE in a subquery.
Allow mixing of traditional and SQL-standard LIMIT/OFFSET syntax (Tom Lane)
Extend the supported frame options in window functions (Hitoshi Harada)
Frames can now start with CURRENT ROW, and the ROWS n PRECEDING/FOLLOWING options are now supported.
Make SELECT INTO and CREATE TABLE AS return row counts to the client in their command tags (Boszormenyi Zoltan)
This can save an entire round-trip to the client, allowing result counts and pagination to be calculated without an additional COUNT query.
Speed up CREATE DATABASE by deferring flushes to disk (Andres Freund, Greg Stark)
Allow comments on columns of tables, views, and composite types only, not other relation types such as indexes and TOAST tables (Tom Lane)
Allow the creation of enumerated types containing no values (Bruce Momjian)
Let values of columns having storage type MAIN remain on the main heap page unless the row cannot fit on a page (Kevin Grittner)
Previously MAIN values were forced out to TOAST tables until the row size was less than one-quarter of the page size.
Implement IF EXISTS for ALTER TABLE DROP COLUMN and ALTER TABLE DROP CONSTRAINT (Andres Freund)
Allow ALTER TABLE commands that rewrite tables to skip WAL logging (Itagaki Takahiro)
Such operations either produce a new copy of the table or are rolled back, so WAL archiving can be skipped, unless running in continuous archiving mode. This reduces I/O overhead and improves performance.
Fix failure of ALTER TABLE table ADD COLUMN col serial when done by non-owner of table (Tom Lane)
Add support for copying COMMENTS and STORAGE settings in CREATE TABLE ... LIKE commands (Itagaki Takahiro)
Add a shortcut for copying all properties in CREATE TABLE ... LIKE commands (Itagaki Takahiro)
Add the SQL-standard CREATE TABLE ... OF type command (Peter Eisentraut)
This allows creation of a table that matches an existing composite type. Additional constraints and defaults can be specified in the command.
Add deferrable unique constraints (Dean Rasheed)
This allows mass updates, such as UPDATE tab SET col = col + 1, to work reliably on columns that have unique indexes or are marked as primary keys. If the constraint is specified as DEFERRABLE it will be checked at the end of the statement, rather than after each row is updated. The constraint check can also be deferred until the end of the current transaction, allowing such updates to be spread over multiple SQL commands.
Add exclusion constraints (Jeff Davis)
Exclusion constraints generalize uniqueness constraints by allowing arbitrary comparison operators, not just equality. They are created with the CREATE TABLE CONSTRAINT ... EXCLUDE clause. The most common use of exclusion constraints is to specify that column entries must not overlap, rather than simply not be equal. This is useful for time periods and other ranges, as well as arrays. This feature enhances checking of data integrity for many calendaring, time-management, and scientific applications.
Improve uniqueness-constraint violation error messages to report the values causing the failure (Itagaki Takahiro)
For example, a uniqueness constraint violation might now report Key (x)=(2) already exists.
Add the ability to make mass permission changes across a whole schema using the new GRANT/REVOKE IN SCHEMA clause (Petr Jelinek)
This simplifies management of object permissions and makes it easier to utilize database roles for application data security.
Add ALTER DEFAULT PRIVILEGES command to control privileges of objects created later (Petr Jelinek)
This greatly simplifies the assignment of object privileges in a complex database application. Default privileges can be set for tables, views, sequences, and functions. Defaults may be assigned on a per-schema basis, or database-wide.
Add the ability to control large object (BLOB) permissions with GRANT/REVOKE (KaiGai Kohei)
Formerly, any database user could read or modify any large object. Read and write permissions can now be granted and revoked per large object, and the ownership of large objects is tracked.
Make LISTEN/NOTIFY store pending events in a memory queue, rather than in a system table (Joachim Wieland)
This substantially improves performance, while retaining the existing features of transactional support and guaranteed delivery.
Allow NOTIFY to pass an optional "payload" string to listeners (Joachim Wieland)
This greatly improves the usefulness of LISTEN/NOTIFY as a general-purpose event queue system.
Allow CLUSTER on all per-database system catalogs (Tom Lane)
Shared catalogs still cannot be clustered.
Accept COPY ... CSV FORCE QUOTE * (Itagaki Takahiro)
Now * can be used as shorthand for "all columns" in the FORCE QUOTE clause.
Add new COPY syntax that allows options to be specified inside parentheses (Robert Haas, Emmanuel Cecchet)
This allows greater flexibility for future COPY options. The old syntax is still supported, but only for pre-existing options.
Allow EXPLAIN to output in XML, JSON, or YAML format (Robert Haas, Greg Sabino Mullane)
The new output formats are easily machine-readable, supporting the development of new tools for analysis of EXPLAIN output.
Add new BUFFERS option to report query buffer usage during EXPLAIN ANALYZE (Itagaki Takahiro)
This allows better query profiling for individual queries. Buffer usage is no longer reported in the output for log_statement_stats and related settings.
Add hash usage information to EXPLAIN output (Robert Haas)
Add new EXPLAIN syntax that allows options to be specified inside parentheses (Robert Haas)
This allows greater flexibility for future EXPLAIN options. The old syntax is still supported, but only for pre-existing options.
Change VACUUM FULL to rewrite the entire table and rebuild its indexes, rather than moving individual rows around to compact space (Itagaki Takahiro, Tom Lane)
The previous method was usually slower and caused index bloat. Note that the new method will use more disk space transiently during VACUUM FULL; potentially as much as twice the space normally occupied by the table and its indexes.
Add new VACUUM syntax that allows options to be specified inside parentheses (Itagaki Takahiro)
This allows greater flexibility for future VACUUM options. The old syntax is still supported, but only for pre-existing options.
Allow an index to be named automatically by omitting the index name in CREATE INDEX (Tom Lane)
By default, multicolumn indexes are now named after all their columns; and index expression columns are now named based on their expressions (Tom Lane)
Reindexing shared system catalogs is now fully transactional and crash-safe (Tom Lane)
Formerly, reindexing a shared index was only allowed in standalone mode, and a crash during the operation could leave the index in worse condition than it was before.
Add point_ops operator class for GiST (Teodor Sigaev)
This feature permits GiST indexing of point columns. The index can be used for several types of queries such as point <@ polygon (point is in polygon). This should make many PostGIS queries faster.
Use red-black binary trees for GIN index creation (Teodor Sigaev)
Red-black trees are self-balancing. This avoids slowdowns in cases where the input is in nonrandom order.
Allow bytea values to be written in hex notation (Peter Eisentraut)
The server parameter bytea_output controls
whether hex or traditional format is used for bytea
output. Libpq's PQescapeByteaConn()
function automatically
uses the hex format when connected to PostgreSQL 9.0
or newer servers. However, pre-9.0 libpq versions will not
correctly process hex format from newer servers.
The new hex format will be directly compatible with more applications that use binary data, allowing them to store and retrieve it without extra conversion. It is also significantly faster to read and write than the traditional format.
Allow server parameter extra_float_digits to be increased to 3 (Tom Lane)
The previous maximum extra_float_digits setting was 2. There are cases where 3 digits are needed to dump and restore float4 values exactly. pg_dump will now use the setting of 3 when dumping from a server that allows it.
Tighten input checking for int2vector values (Caleb Welton)
Add prefix support in synonym dictionaries (Teodor Sigaev)
Add filtering dictionaries (Teodor Sigaev)
Filtering dictionaries allow tokens to be modified then passed to subsequent dictionaries.
Allow underscores in email-address tokens (Teodor Sigaev)
Use more standards-compliant rules for parsing URL tokens (Tom Lane)
Allow function calls to supply parameter names and match them to named parameters in the function definition (Pavel Stehule)
For example, if a function is defined to take parameters a and b, it can be called with func(a := 7, b := 12) or func(b := 12, a := 7).
Support locale-specific regular expression processing with UTF-8 server encoding (Tom Lane)
Locale-specific regular expression functionality includes case-insensitive matching and locale-specific character classes. Previously, these features worked correctly for non-ASCII characters only if the database used a single-byte server encoding (such as LATIN1). They will still misbehave in multi-byte encodings other than UTF-8.
Add support for scientific notation in to_char()
(EEEE
specification)
(Pavel Stehule, Brendan Jurd)
Make to_char()
honor FM
(fill mode) in Y, YY, and
YYY specifications (Bruce Momjian, Tom Lane)
It was already honored by YYYY.
Fix to_char()
to output localized numeric and monetary
strings in the correct encoding on Windows
(Hiroshi Inoue, Itagaki Takahiro, Bruce Momjian)
Correct calculations of "overlaps" and "contains" operations for polygons (Teodor Sigaev)
The polygon && (overlaps) operator formerly just checked to see if the two polygons' bounding boxes overlapped. It now does a more correct check. The polygon @> and <@ (contains/contained by) operators formerly checked to see if one polygon's vertexes were all contained in the other; this can wrongly report "true" for some non-convex polygons. Now they check that all line segments of one polygon are contained in the other.
Allow aggregate functions to use ORDER BY (Andrew Gierth)
For example, this is now supported: array_agg(a ORDER BY b). This is useful with aggregates for which the order of input values is significant, and eliminates the need to use a nonstandard subquery to determine the ordering.
Multi-argument aggregate functions can now use DISTINCT (Andrew Gierth)
Add the string_agg()
aggregate function to combine values into a single
string (Pavel Stehule)
Aggregate functions that are called with DISTINCT are now passed NULL values if the aggregate transition function is not marked as STRICT (Andrew Gierth)
For example, agg(DISTINCT x) might pass a NULL x
value to agg()
. This is more consistent with the behavior
in non-DISTINCT cases.
Add pg_table_size()
and pg_indexes_size()
to provide a more
user-friendly interface to the pg_relation_size()
function (Bernd Helmle)
Add has_sequence_privilege()
for sequence permission checking (Abhijit Menon-Sen)
Update the information_schema views to conform to SQL:2008 (Peter Eisentraut)
Make the information_schema views correctly display maximum octet lengths for char and varchar columns (Peter Eisentraut)
Speed up information_schema privilege views (Joachim Wieland)
Support execution of anonymous code blocks using the DO statement (Petr Jelinek, Joshua Tolley, Hannu Valtonen)
This allows execution of server-side code without the need to create and delete a temporary function definition. Code can be executed in any language for which the user has permissions to define a function.
Implement SQL-standard-compliant per-column triggers (Itagaki Takahiro)
Such triggers are fired only when the specified column(s) are affected by the query, e.g. appear in an UPDATE's SET list.
Add the WHEN clause to CREATE TRIGGER to allow control over whether a trigger is fired (Itagaki Takahiro)
While the same type of check can always be performed inside the trigger, doing it in an external WHEN clause can have performance benefits.
Add the OR REPLACE clause to CREATE LANGUAGE (Tom Lane)
This is helpful to optionally install a language if it does not already exist, and is particularly helpful now that PL/pgSQL is installed by default.
Install PL/pgSQL by default (Bruce Momjian)
The language can still be removed from a particular database if the administrator has security or performance concerns about making it available.
Improve handling of cases where PL/pgSQL variable names conflict with identifiers used in queries within a function (Tom Lane)
The default behavior is now to throw an error when there is a conflict, so as to avoid surprising behaviors. This can be modified, via the configuration parameter plpgsql.variable_conflict or the per-function option #variable_conflict, to allow either the variable or the query-supplied column to be used. In any case PL/pgSQL will no longer attempt to substitute variables in places where they would not be syntactically valid.
Make PL/pgSQL use the main lexer, rather than its own version (Tom Lane)
This ensures accurate tracking of the main system's behavior for details such as string escaping. Some user-visible details, such as the set of keywords considered reserved in PL/pgSQL, have changed in consequence.
Avoid throwing an unnecessary error for an invalid record reference (Tom Lane)
An error is now thrown only if the reference is actually fetched, rather than whenever the enclosing expression is reached. For example, many people have tried to do this in triggers:
if TG_OP = 'INSERT' and NEW.col1 = ... then
This will now actually work as expected.
Improve PL/pgSQL's ability to handle row types with dropped columns (Pavel Stehule)
Allow input parameters to be assigned values within PL/pgSQL functions (Steve Prentice)
Formerly, input parameters were treated as being declared CONST, so the function's code could not change their values. This restriction has been removed to simplify porting of functions from other DBMSes that do not impose the equivalent restriction. An input parameter now acts like a local variable initialized to the passed-in value.
Improve error location reporting in PL/pgSQL (Tom Lane)
Add count and ALL options to MOVE FORWARD/BACKWARD in PL/pgSQL (Pavel Stehule)
Allow PL/pgSQL's WHERE CURRENT OF to use a cursor variable (Tom Lane)
Allow PL/pgSQL's OPEN cursor FOR EXECUTE to use parameters (Pavel Stehule, Itagaki Takahiro)
This is accomplished with a new USING clause.
Add new PL/Perl functions: quote_literal()
,
quote_nullable()
, quote_ident()
,
encode_bytea()
, decode_bytea()
,
looks_like_number()
,
encode_array_literal()
,
encode_array_constructor()
(Tim Bunce)
Add server parameter plperl.on_init to specify a PL/Perl initialization function (Tim Bunce)
plperl.on_plperl_init and plperl.on_plperlu_init are also available for initialization that is specific to the trusted or untrusted language respectively.
Support END blocks in PL/Perl (Tim Bunce)
END blocks do not currently allow database access.
Allow use strict in PL/Perl (Tim Bunce)
Perl strict checks can also be globally enabled with the new server parameter plperl.use_strict.
Allow require in PL/Perl (Tim Bunce)
This basically tests to see if the module is loaded, and if not, generates an error. It will not allow loading of modules that the administrator has not preloaded via the initialization parameters.
Allow use feature in PL/Perl if Perl version 5.10 or later is used (Tim Bunce)
Verify that PL/Perl return values are valid in the server encoding (Andrew Dunstan)
Add Unicode support in PL/Python (Peter Eisentraut)
Strings are automatically converted from/to the server encoding as necessary.
Improve bytea support in PL/Python (Caleb Welton)
Bytea values passed into PL/Python are now represented as binary, rather than the PostgreSQL bytea text format. Bytea values containing null bytes are now also output properly from PL/Python. Passing of boolean, integer, and float values was also improved.
Support arrays as parameters and return values in PL/Python (Peter Eisentraut)
Improve mapping of SQL domains to Python types (Peter Eisentraut)
Add Python 3 support to PL/Python (Peter Eisentraut)
The new server-side language is called plpython3u. This cannot be used in the same session with the Python 2 server-side language.
Improve error location and exception reporting in PL/Python (Peter Eisentraut)
Add an --analyze-only option to vacuumdb, to analyze without vacuuming (Bruce Momjian)
Add support for quoting/escaping the values of psql variables as SQL strings or identifiers (Pavel Stehule, Robert Haas)
For example, :'var' will produce the value of var quoted and properly escaped as a literal string, while :"var" will produce its value quoted and escaped as an identifier.
Ignore a leading UTF-8-encoded Unicode byte-order marker in script files read by psql (Itagaki Takahiro)
This is enabled when the client encoding is UTF-8. It improves compatibility with certain editors, mostly on Windows, that insist on inserting such markers.
Fix psql --file - to properly honor --single-transaction (Bruce Momjian)
Avoid overwriting of psql's command-line history when two psql sessions are run concurrently (Tom Lane)
Improve psql's tab completion support (Itagaki Takahiro)
Show \timing output when it is enabled, regardless of "quiet" mode (Peter Eisentraut)
Improve display of wrapped columns in psql (Roger Leigh)
This behavior is now the default. The previous formatting is available by using \pset linestyle old-ascii.
Allow psql to use fancy Unicode line-drawing characters via \pset linestyle unicode (Roger Leigh)
Make \d show child tables that inherit from the specified parent (Damien Clochard)
\d shows only the number of child tables, while \d+ shows the names of all child tables.
Show definitions of index columns in \d index_name (Khee Chin)
The definition is useful for expression indexes.
Show a view's defining query only in \d+, not in \d (Peter Eisentraut)
Always including the query was deemed overly verbose.
Make pg_dump/pg_restore --clean also remove large objects (Itagaki Takahiro)
Fix pg_dump to properly dump large objects when standard_conforming_strings is enabled (Tom Lane)
The previous coding could fail when dumping to an archive file and then generating script output from pg_restore.
pg_restore now emits large-object data in hex format when generating script output (Tom Lane)
This could cause compatibility problems if the script is then loaded into a pre-9.0 server. To work around that, restore directly to the server, instead.
Allow pg_dump to dump comments attached to columns of composite types (Taro Minowa (Higepon))
Make pg_dump --verbose output the pg_dump and server versions in text output mode (Jim Cox, Tom Lane)
These were already provided in custom output mode.
pg_restore now complains if any command-line arguments remain after the switches and optional file name (Tom Lane)
Previously, it silently ignored any such arguments.
Allow pg_ctl to be used safely to start the postmaster during a system reboot (Tom Lane)
Previously, pg_ctl's parent process could have been mistakenly identified as a running postmaster based on a stale postmaster lock file, resulting in a transient failure to start the database.
Give pg_ctl the ability to initialize the database (by invoking initdb) (Zdenek Kotala)
Add new libpq functions
PQconnectdbParams()
and PQconnectStartParams()
(Guillaume
Lelarge)
These functions are similar to PQconnectdb()
and
PQconnectStart()
except that they accept a null-terminated
array of connection options, rather than requiring all options to
be provided in a single string.
Add libpq functions PQescapeLiteral()
and PQescapeIdentifier()
(Robert Haas)
These functions return appropriately quoted and escaped SQL string
literals and identifiers. The caller is not required to pre-allocate
the string result, as is required by PQescapeStringConn()
.
Add support for a per-user service file (.pg_service.conf), which is checked before the site-wide service file (Peter Eisentraut)
Properly report an error if the specified libpq service cannot be found (Peter Eisentraut)
Add TCP keepalive settings in libpq (Tollef Fog Heen, Fujii Masao, Robert Haas)
Keepalive settings were already supported on the server end of TCP connections.
Avoid extra system calls to block and unblock SIGPIPE in libpq, on platforms that offer alternative methods (Jeremy Kerr)
When a .pgpass-supplied password fails, mention where the password came from in the error message (Bruce Momjian)
Load all SSL certificates given in the client certificate file (Tom Lane)
This improves support for indirectly-signed SSL certificates.
Add SQLDA (SQL Descriptor Area) support to ecpg (Boszormenyi Zoltan)
Add the DESCRIBE [ OUTPUT ] statement to ecpg (Boszormenyi Zoltan)
Add an ECPGtransactionStatus function to return the current transaction status (Bernd Helmle)
Add the string data type in ecpg Informix-compatibility mode (Boszormenyi Zoltan)
Allow ecpg to use new and old variable names without restriction (Michael Meskes)
Allow ecpg to use variable names in
free()
(Michael Meskes)
Make ecpg_dynamic_type()
return zero for non-SQL3 data
types (Michael Meskes)
Previously it returned the negative of the data type OID. This could be confused with valid type OIDs, however.
Support long long types on platforms that already have 64-bit long (Michael Meskes)
Add out-of-scope cursor support in ecpg's native mode (Boszormenyi Zoltan)
This allows DECLARE to use variables that are not in scope when OPEN is called. This facility already existed in ecpg's Informix-compatibility mode.
Allow dynamic cursor names in ecpg (Boszormenyi Zoltan)
Allow ecpg to use noise words FROM and IN in FETCH and MOVE (Boszormenyi Zoltan)
Enable client thread safety by default (Bruce Momjian)
The thread-safety option can be disabled with configure --disable-thread-safety.
Add support for controlling the Linux out-of-memory killer (Alex Hunsaker, Tom Lane)
Now that /proc/self/oom_adj allows disabling of the Linux out-of-memory (OOM) killer, it's recommendable to disable OOM kills for the postmaster. It may then be desirable to re-enable OOM kills for the postmaster's child processes. The new compile-time option LINUX_OOM_ADJ allows the killer to be reactivated for child processes.
New Makefile targets world, install-world, and installcheck-world (Andrew Dunstan)
These are similar to the existing all, install, and installcheck targets, but they also build the HTML documentation, build and test contrib, and test server-side languages and ecpg.
Add data and documentation installation location control to PGXS Makefiles (Mark Cave-Ayland)
Add Makefile rules to build the PostgreSQL documentation as a single HTML file or as a single plain-text file (Peter Eisentraut, Bruce Momjian)
Support compiling on 64-bit Windows and running in 64-bit mode (Tsutomu Yamada, Magnus Hagander)
This allows for large shared memory sizes on Windows.
Support server builds using Visual Studio 2008 (Magnus Hagander)
Distribute prebuilt documentation in a subdirectory tree, rather than as tar archive files inside the distribution tarball (Peter Eisentraut)
For example, the prebuilt HTML documentation is now in doc/src/sgml/html/; the manual pages are packaged similarly.
Make the server's lexer reentrant (Tom Lane)
This was needed for use of the lexer by PL/pgSQL.
Improve speed of memory allocation (Tom Lane, Greg Stark)
User-defined constraint triggers now have entries in pg_constraint as well as pg_trigger (Tom Lane)
Because of this change, pg_constraint.pgconstrname is now redundant and has been removed.
Add system catalog columns pg_constraint.conindid and pg_trigger.tgconstrindid to better document the use of indexes for constraint enforcement (Tom Lane)
Allow multiple conditions to be communicated to backends using a single operating system signal (Fujii Masao)
This allows new features to be added without a platform-specific constraint on the number of signal conditions.
Improve source code test coverage, including contrib, PL/Python, and PL/Perl (Peter Eisentraut, Andrew Dunstan)
Remove the use of flat files for system table bootstrapping (Tom Lane, Alvaro Herrera)
This improves performance when using many roles or databases, and eliminates some possible failure conditions.
Automatically generate the initial contents of pg_attribute for "bootstrapped" catalogs (John Naylor)
This greatly simplifies changes to these catalogs.
Split the processing of INSERT/UPDATE/DELETE operations out of execMain.c (Marko Tiikkaja)
Updates are now executed in a separate ModifyTable node. This change is necessary infrastructure for future improvements.
Simplify translation of psql's SQL help text (Peter Eisentraut)
Reduce the lengths of some file names so that all file paths in the distribution tarball are less than 100 characters (Tom Lane)
Some decompression programs have problems with longer file paths.
Add a new ERRCODE_INVALID_PASSWORD SQLSTATE error code (Bruce Momjian)
With authors' permissions, remove the few remaining personal source code copyright notices (Bruce Momjian)
The personal copyright notices were insignificant but the community occasionally had to answer questions about them.
Add new documentation section about running PostgreSQL in non-durable mode to improve performance (Bruce Momjian)
Restructure the HTML documentation Makefile rules to make their dependency checks work correctly, avoiding unnecessary rebuilds (Peter Eisentraut)
Use DocBook XSL stylesheets for man page building, rather than Docbook2X (Peter Eisentraut)
This changes the set of tools needed to build the man pages.
Improve PL/Perl code structure (Tim Bunce)
Improve error context reports in PL/Perl (Alexey Klyukin)
Note that these requirements do not apply when building from a distribution tarball, since tarballs include the files that these programs are used to build.
Require Autoconf 2.63 to build configure (Peter Eisentraut)
Require Flex 2.5.31 or later to build from a CVS checkout (Tom Lane)
Require Perl version 5.8 or later to build from a CVS checkout (John Naylor, Andrew Dunstan)
Use a more modern API for Bonjour (Tom Lane)
Bonjour support now requires OS X 10.3 or later. The older API has been deprecated by Apple.
Add spinlock support for the SuperH architecture (Nobuhiro Iwamatsu)
Allow non-GCC compilers to use inline functions if they support them (Kurt Harriman)
Remove support for platforms that don't have a working 64-bit integer data type (Tom Lane)
Restructure use of LDFLAGS to be more consistent across platforms (Tom Lane)
LDFLAGS is now used for linking both executables and shared libraries, and we add on LDFLAGS_EX when linking executables, or LDFLAGS_SL when linking shared libraries.
Make backend header files safe to include in C++ (Kurt Harriman, Peter Eisentraut)
These changes remove keyword conflicts that previously made C++ usage difficult in backend code. However, there are still other complexities when using C++ for backend functions. extern "C" { } is still necessary in appropriate places, and memory management and error handling are still problematic.
Add AggCheckCallContext()
for use in detecting if a C function is
being called as an aggregate (Hitoshi Harada)
Change calling convention for SearchSysCache()
and related
functions to avoid hard-wiring the maximum number of cache keys
(Robert Haas)
Existing calls will still work for the moment, but can be expected to break in 9.1 or later if not converted to the new style.
Require calls of fastgetattr()
and
heap_getattr()
backend macros to provide a non-NULL fourth
argument (Robert Haas)
Custom typanalyze functions should no longer rely on VacAttrStats.attr to determine the type of data they will be passed (Tom Lane)
This was changed to allow collection of statistics on index columns for which the storage type is different from the underlying column data type. There are new fields that tell the actual datatype being analyzed.
Add parser hooks for processing ColumnRef and ParamRef nodes (Tom Lane)
Add a ProcessUtility hook so loadable modules can control utility commands (Itagaki Takahiro)
Add contrib/pg_upgrade to support in-place upgrades (Bruce Momjian)
This avoids the requirement of dumping/reloading the database when upgrading to a new major release of PostgreSQL, thus reducing downtime by orders of magnitude. It supports upgrades to 9.0 from PostgreSQL 8.3 and 8.4.
Add support for preserving relation relfilenode values during binary upgrades (Bruce Momjian)
Add support for preserving pg_type and pg_enum OIDs during binary upgrades (Bruce Momjian)
Move data files within tablespaces into PostgreSQL-version-specific subdirectories (Bruce Momjian)
This simplifies binary upgrades.
Add multithreading option (-j) to contrib/pgbench (Itagaki Takahiro)
This allows multiple CPUs to be used by pgbench, reducing the risk of pgbench itself becoming the test bottleneck.
Add \shell and \setshell meta commands to contrib/pgbench (Michael Paquier)
New features for contrib/dict_xsyn (Sergey Karpov)
The new options are matchorig, matchsynonyms, and keepsynonyms.
Add full text dictionary contrib/unaccent (Teodor Sigaev)
This filtering dictionary removes accents from letters, which makes full-text searches over multiple languages much easier.
Add dblink_get_notify()
to contrib/dblink (Marcus Kempe)
This allows asynchronous notifications in dblink.
Improve contrib/dblink's handling of dropped columns (Tom Lane)
This affects dblink_build_sql_insert()
and related functions. These functions now number columns according
to logical not physical column numbers.
Greatly increase contrib/hstore's data length limit, and add B-tree and hash support so GROUP BY and DISTINCT operations are possible on hstore columns (Andrew Gierth)
New functions and operators were also added. These improvements make hstore a full-function key-value store embedded in PostgreSQL.
Add contrib/passwordcheck to support site-specific password strength policies (Laurenz Albe)
The source code of this module should be modified to implement site-specific password policies.
Add contrib/pg_archivecleanup tool (Simon Riggs)
This is designed to be used in the archive_cleanup_command server parameter, to remove no-longer-needed archive files.
Add query text to contrib/auto_explain output (Andrew Dunstan)
Add buffer access counters to contrib/pg_stat_statements (Itagaki Takahiro)
Update contrib/start-scripts/linux to use /proc/self/oom_adj to disable the Linux out-of-memory (OOM) killer (Alex Hunsaker, Tom Lane)


While tutoring a 6th grader today, I went into my bag to pull out my 1. {{words.word1}}, and the box of 2. {{words.word2}} I forgot I had in there fell out. He asked what was in the box. I had to spend the next 3. {{words.word3}} minutes trying to convince him that it was 4. {{words.word4}} wear for med school students, and I had them in preparation for applying to medical school.


This is the sample OS Adaptation layer which is used by the GPIO driver. The OSAL layer can be ported in either of the following manners to a native OS: More...
#include <ti/osal/osal.h>
Macros | |
| #define | GPIO_osalAssert(expr) OSAL_Assert(expr) |
| Assert API. If expression is true then it will stay in the while loop. More... | |
| #define | GPIO_osalCreateBlockingLock(count, params) (SemaphoreP_create((count),(params))) |
| The macro is used by the GPIO driver to create a semaphore for each GPIO opened in blocking mode. Semaphores created should initially be created with a count of 0 i.e. unavailable. More... | |
| #define | GPIO_osalDeleteBlockingLock(X) (SemaphoreP_delete(X)) |
| The macro is used by the GPIO driver to delete a previously created semaphore. This is called when a GPIO opened in blocking mode is being closed. More... | |
| #define | GPIO_osalSemParamsInit(params) (SemaphoreP_Params_init(params)) |
| Initialize params structure to default values. More... | |
| #define | GPIO_osalPendLock(X, Y) (SemaphoreP_pend((X),(Y))) |
| The macro is used by the GPIO driver to pend on a semaphore This is called when an application tries to receive data on a blocking when there is no data available. Since all semaphores are initially created to be unavailable; this will cause the application to block. More... | |
| #define | GPIO_osalPostLock(X) (SemaphoreP_post(X)) |
| The macro is used by the GPIO driver to post the semaphore The driver posts the semaphore once data is received on a specific. More... | |
| #define | GPIO_osalHardwareIntDisable() (HwiP_disable()) |
| Function to disable interrupts to enter a critical region. More... | |
| #define | GPIO_osalHardwareIntRestore(X) (HwiP_restore(X)) |
| Function to restore interrupts to exit a critical region. More... | |
| #define | GPIO_osalHardwareIntDestruct(X, Y) (Osal_DeleteInterrupt((X),(Y))) |
| Function to deregister a interrupt. More... | |
| #define | GPIO_osalRegisterInterrupt(X, Y) (Osal_RegisterInterrupt((X),(Y))) |
| Function to register an interrupt. More... | |
| #define | GPIO_osalHwiParamsInit(X) (HwiP_Params_init(X)) |
| Function to initialize hardware interrupt parameters. More... | |
| #define | GPIO_osalHardwareIntrDisable(X, Y) (Osal_DisableInterrupt((X),(Y))) |
| Function to disable specific hardware interrupt. More... | |
| #define | GPIO_osalHardwareIntrEnable(X, Y) (Osal_EnableInterrupt((X),(Y))) |
| Function to enable specific hardware interrupt. More... | |
| #define | GPIO_osalHardwareIntrClear(X, Y) (Osal_ClearInterrupt((X),(Y))) |
| Function to clear specific hardware interrupt. More... | |
| #define | GPIO_osalMuxIntcSetup(X, Y) (MuxIntcP_create((X), (Y))) |
| Function to Setup Interrupt Controller Mux. More... | |
| #define | GPIO_osalMuxIntcEnableSysInt(X, Y) (MuxIntcP_enableInEvent((X), (Y))) |
| Function to enable Intc Mux system event. More... | |
| #define | GPIO_osalMuxIntcDisableSysInt(X, Y) (MuxIntcP_disableInEvent((X), (Y))) |
| Function to disable Intc Mux system event. More... | |
| #define | GPIO_osalMuxIntcClearSysInt(X, Y) (MuxIntcP_clearInEvent((X), (Y))) |
| Function to clear Intc Mux system event. More... | |
This is the sample OS Adaptation layer which is used by the GPIO driver. The OSAL layer can be ported in either of the following manners to a native OS:
Approach 1:
Use Prebuilt Libraries
Approach 2:
Rebuilt Library
| #define GPIO_osalAssert | ( | expr | ) | OSAL_Assert(expr) |
Assert API. If expression is true then it will stay in the while loop.
| expr | Expression which need to be evaluated. |
| #define GPIO_osalCreateBlockingLock | ( | count, | |
| params | |||
| ) | (SemaphoreP_create((count),(params))) |
The macro is used by the GPIO driver to create a semaphore for each GPIO opened in blocking mode. Semaphores created should initially be created with a count of 0 i.e. unavailable.
| count | Initial count of the semaphore. For binary semaphores, only values of 0 or 1 are valid. |
| params | Pointer to the instance configuration parameters. NULL denotes to use the default parameters (SemOSAL default parameters as noted in SemOSAL_Params. |
| #define GPIO_osalDeleteBlockingLock | ( | X | ) | (SemaphoreP_delete(X)) |
The macro is used by the GPIO driver to delete a previously created semaphore. This is called when a GPIO opened in blocking mode is being closed.
Prototype: The following is the C prototype for the expected OSAL API.
void SemOSAL_delete(void* semHandle)
Parameter
Semaphore Handle returned by the create semaphore
Return Value
Not Applicable
| #define GPIO_osalHardwareIntDestruct | ( | X, | |
| Y | |||
| ) | (Osal_DeleteInterrupt((X),(Y))) |
Function to deregister a interrupt.
Prototype: The following is the C prototype for the expected OSAL API.
int HwiOSAL_deregisterInterrupt(void* hwiPtr)
Parameter
Interrupt handler
Return Value
status of operation
| #define GPIO_osalHardwareIntDisable | ( | ) | (HwiP_disable()) |
Function to disable interrupts to enter a critical region.
Prototype: The following is the C prototype for the expected OSAL API.
void HwiOSAL_enterCritical()
Parameter
Not Applicable
Return Value
Interrupt key
| #define GPIO_osalHardwareIntrClear | ( | X, | |
| Y | |||
| ) | (Osal_ClearInterrupt((X),(Y))) |
Function to clear specific hardware interrupt.
Prototype: The following is the C prototype for the expected OSAL API.
void GPIO_osalHardwareIntrClear(unsigned int intrNum)
Parameter
Interrupt number
| #define GPIO_osalHardwareIntrDisable | ( | X, | |
| Y | |||
| ) | (Osal_DisableInterrupt((X),(Y))) |
Function to disable specific hardware interrupt.
Prototype: The following is the C prototype for the expected OSAL API.
void HwiOSAL_disableInterrupt(unsigned int intrNum)
Parameter
Interrupt number
| #define GPIO_osalHardwareIntrEnable | ( | X, | |
| Y | |||
| ) | (Osal_EnableInterrupt((X),(Y))) |
Function to enable specific hardware interrupt.
Prototype: The following is the C prototype for the expected OSAL API.
void HwiOSAL_enableInterrupt(unsigned int intrNum)
Parameter
Interrupt number
| #define GPIO_osalHardwareIntRestore | ( | X | ) | (HwiP_restore(X)) |
Function to restore interrupts to exit a critical region.
Prototype: The following is the C prototype for the expected OSAL API.
void HwiOSAL_exitCritical(int key)
Parameter
Interrupt key
Return Value
Not Applicable
| #define GPIO_osalHwiParamsInit | ( | X | ) | (HwiP_Params_init(X)) |
Function to initialize hardware interrupt parameters.
Prototype: The following is the C prototype for the expected OSAL API.
void HwiP_Params_init(X)
Parameter
params pointer to the hardware interrupts parameter structure
| #define GPIO_osalMuxIntcClearSysInt | ( | X, | |
| Y | |||
| ) | (MuxIntcP_clearInEvent((X), (Y))) |
Function to clear Intc Mux system event.
Prototype: The following is the C prototype for the expected OSAL API.
void MuxIntcP_clearInEvent(int cicNum, int cicEventId)
Parameter
Interrupt Controller mux number
Parameter
Interrupt Controller mux input event ID
| #define GPIO_osalMuxIntcDisableSysInt | ( | X, | |
| Y | |||
| ) | (MuxIntcP_disableInEvent((X), (Y))) |
Function to disable Intc Mux system event.
Prototype: The following is the C prototype for the expected OSAL API.
void MuxIntcP_disableInEvent(int32_t muxNum, int32_t muxInEvent)
Parameter
Interrupt Controller mux number
Parameter
Interrupt Controller mux input event ID
| #define GPIO_osalMuxIntcEnableSysInt | ( | X, | |
| Y | |||
| ) | (MuxIntcP_enableInEvent((X), (Y))) |
Function to enable Intc Mux system event.
Prototype: The following is the C prototype for the expected OSAL API.
void MuxIntcP_enableInEvent(int32_t muxNum, int32_t muxInEvent)
Parameter
Interrupt Controller mux number
Parameter
Interrupt Controller mux input event ID
| #define GPIO_osalMuxIntcSetup | ( | X, | |
| Y | |||
| ) | (MuxIntcP_create((X), (Y))) |
Function to Setup Interrupt Controller Mux.
Prototype: The following is the C prototype for the expected OSAL API.
void MuxIntcP_create(MuxIntcP_inParams *inParams, MuxIntcP_outParams *outParams)
Parameter
Pointer to the instance configuration input parameters.
Parameter
Pointer to the instance configuration output parameters.
| #define GPIO_osalPendLock | ( | X, | |
| Y | |||
| ) | (SemaphoreP_pend((X),(Y))) |
The macro is used by the GPIO driver to pend on a semaphore This is called when an application tries to receive data on a blocking when there is no data available. Since all semaphores are initially created to be unavailable; this will cause the application to block.
Prototype: The following is the C prototype for the expected OSAL API.
void SemOSAL_pend(void* semHandle)
Parameter
Semaphore Handle
Return Value
Not Applicable
| #define GPIO_osalPostLock | ( | X | ) | (SemaphoreP_post(X)) |
The macro is used by the GPIO driver to post the semaphore The driver posts the semaphore once data is received on a specific.
Prototype: The following is the C prototype for the expected OSAL API.
void SemOSAL_post(void* semHandle)
Parameter
Semaphore Handle
Return Value
Not Applicable
| #define GPIO_osalRegisterInterrupt | ( | X, | |
| Y | |||
| ) | (Osal_RegisterInterrupt((X),(Y))) |
Function to register an interrupt.
Prototype: The following is the C prototype for the expected OSAL API.
int OSAL_registerInterrupt(X,Y)
Parameter
Interrupt number
Parameter
eventID
Parameter
entry entry function of the hardware interrupt
Parameter
arg argument passed into the entry function
Parameter
priority
Return Value
Interrupt handler
| #define GPIO_osalSemParamsInit | ( | params | ) | (SemaphoreP_Params_init(params)) |
Initialize params structure to default values.
The default parameters are:
| params | Pointer to the instance configuration parameters. |


Select like a Boss
Now you can select link's text just like a regular text (like in Opera'12 browser) - Select like a Boss ;)
| select | ↔ | like a regular text |
| drag | ↕ | up or down |
Enjoy! (and share the extension with other people)
Notice: some links can be unselectable
If you want to use the extension in the incognito mode too, do not forget to enable the checkbox [Allow in incognito] on the extensions page.


Email address:
First Name:
Last Name:
Username:
@
Age:
Password:
Confirm Password:
Address:
First Hobby:
Second Hobby:
Third Hobby:
Date of Birth
Day
--Please Select--
Month
--Please Select--
Year
--Please Select--
Gender:
Male
Female
Accept terms and conditions
Submit


Set of functions for Regression Discontinuity Design ('RDD'), for data visualisation, estimation and testing.
| Version: | 0.4.0 |
| Depends: | AER, np |
| Imports: | KernSmooth, ggplot2, rdd, sandwich, lmtest, Formula, locpol, methods |
| Suggests: | stats4, car, knitr, testthat |
| Published: | 2015-07-27 |
| Author: | Matthieu Stigler [aut], Bastiaan Quast [aut, cre] |
| Maintainer: | Bastiaan Quast <bquast at gmail.com> |
| BugReports: | https://github.com/bquast/RDDtools/issues |
| License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| URL: | https://github.com/bquast/RDDtools |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| In views: | Econometrics |
| CRAN checks: | rddtools results |
| Reference manual: | rddtools.pdf |
| Vignettes: |
Morocco Data entry |
| Package source: | rddtools_0.4.0.tar.gz |
| Windows binaries: | r-devel: rddtools_0.4.0.zip, r-release: rddtools_0.4.0.zip, r-oldrel: rddtools_0.4.0.zip |
| OS X binaries: | r-release: rddtools_0.4.0.tgz, r-oldrel: rddtools_0.4.0.tgz |
| Reverse suggests: | rddapp |
Please use the canonical form https://CRAN.R-project.org/package=rddtools to link to this page.


[§302D-9] Exclusivity of authorizing functions and rights. No governmental or other entity, other than those expressly granted chartering authority as set forth in this chapter, may assume any charter authorizing function or duty in any form, unless expressly allowed by law. [L 2012, c 130, pt of §2]


Fixes crash reported, and also fixes CheckTxFee helper function to check coins in mempool.
I had to add a 1 sat exception for the validation, I cant find any other way to do it, as the behavior seems different on Alrights system and mine, I think the problem is RPC side, but I can't work it out. 1 sat variation is nothing to worry about I think when the maximum payout is 10,000 sat in any case.


South_Park
South Park is an adult comedy animation show centred around 4 children in the small town of south park. Its humour is often dark involving satirical elements and mocking current real-life events.


--- layout: post title: Code formatting in WordPress date: 2010-11-10 09:40:12.000000000 +02:00 categories: [] tags: [] status: publish type: post published: true post_id: code-formatting-in-wp meta: _edit_last: '1' _wp_old_slug: '' author: login: admin email<EMAIL_ADDRESS>display_name: Radu first_name: '' last_name: '' ---
My first concern when i was getting this blog up, was to set up a code formatting plugin. I had another install of WordPress and there was no default plugin for that. So after typing some keywords in the plugin search came up with the Syntax Highlighter for WordPress which actually uses the SyntaxHighlighter . Searching around i found that Scott Hansleman uses the same plugin, so i decide to settled down with it.
code sample from Scott Hanselman's blog:
[csharp]
// Hello3.cs
using System;
public class Hello3
{
public static void Main(string[] args)
{
Console.WriteLine("Hello, World!");
Console.WriteLine("You entered the following {0} command line arguments:",
args.Length );
for (int i=0; i < args.Length; i++)
{
Console.WriteLine("{0}", args[i]);
}
}
}
[/csharp]