z-logo
Premium
Root surface phosphatase activity in ecotypes of Aegilops peregrina
Author(s) -
Silberbush Moshe,
ShomerIlan Adiva,
Waisel Yoav
Publication year - 1981
Publication title -
physiologia plantarum
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.351
H-Index - 146
eISSN - 1399-3054
pISSN - 0031-9317
DOI - 10.1111/j.1399-3054.1981.tb02740.x
Subject(s) - ecotype , edaphic , calcareous , phosphatase , botany , acid phosphatase , soil water , biology , chemistry , agronomy , ecology , biochemistry , enzyme
The relationships between root surface phosphatase activity and the edaphic factors of their native habitats were investigated in four ecotypes of Aegilops peregrina (Hack.) Maire et Weil. In one set of experiments plants were grown in phosphate‐deficient nutrient solution cultures (5 μ M ) with three pH values: 5.5, 6.5 and 7.5. In a second series, plants were grown in both P‐poor and P‐rich soils. Results showed an optimal activity of the commonly‐described root surface acid phosphatase of pH 4.5–5.0 in the ecotypes Meron (a P‐poor montmorillonitic, typical mediterranean Terra‐Rossa soil) and Har‐Hurshan (a P‐rich calcareous soil). However, in the ecotypes Malkiya (a P‐rich kaolinitic Terra‐Rossa) and Bet‐Guvrin (a P‐rich calcareous soil) the optimal activity of the phosphatase occurred at pH 6.0. The pH level of the growth solution had no effect on the pH of optimal activity of the phosphatase in the ecotypes Malkiya and Bet‐Guvrin, but it somewhat affected their level of activity. Phosphatase activity was stimulated when plant roots were grown in a P‐poor soil, as compared to the activity of those which were grown in a P‐rich soil. Plants of the Malkiya ecotype exhibited the strongest activation of phosphatase as compared to the other three ecotypes. It seems that ecotypes which have evolved in P‐rich soils may regulate their root surface phosphatase activity better than those which have evolved in P‐poor soils.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here