On 11/04/2011 05:01 AM, Cin123 wrote:
I needed a stdint.h header because of uint32_t and that header was missing
in vs2008 sa i take it form vs2010
You can't usually do that. If it were that simple, MS would've probably
released stdint.h in a later VC++2008 service pack.
Why do you actually
Dear all,
For our customer in Dubai, we are looking for references of PostgreSQL
implementations in the Middle East, preferably in the GCC countries, preferably
in the United Arab Emirates (Dubai / Abu Dhabi).
Please help me in this matter.
Thanks in advance!
Best regards,
Jan Geluk
Managin
On Mon, Nov 7, 2011 at 8:41 AM, Konstantin Gredeskoul wrote:
> Does that mean "postgres" superuser is no longer able to also be a
> replication user in 9.1? If so this is not yet updated on the
> Replication wiki.
No. Superuser has the replication privilege by default. But if you granted
the "po
On Fri, Nov 4, 2011 at 10:58 PM, Samba wrote:
> although both master(with replication_timeout) and slave (with tcp timeout
> option in primary_conninfo parameter) closes the connection in quick time
> (based on tcp idle connection timeout), as of now they do not log such
> information. It would
John R Pierce writes:
> generally, built in functionality in PostgreSQL closely follows existing
> SQL database standards and practices, I've not seen or heard of any such
> 'persistent named prepared statements' before in any database system, so
> I suspect the core developers aren't going to
Sean,
I saw your email on PostgreSQL general list about replication.
We are using 9.1.1 and were having the same issue, unable to setup
replication even though following wiki precisely. I was able to
setup replication following wiki steps using PG 9.0.3, but not 9.1.1.
Then I found this page:
h
Hi,
Dne 6.11.2011 15:07, NTPT napsal(a):
> Hi all
>
> I have an idea how to extend postgresql feature set.
>
>
> I sugest named / preparsed / preplamned query mechanizm where named
> query is a simpliest form and preplaned query is the most
> sofisticated (implementation wise). Ie to have abil
On 11/06/11 1:52 PM, NTPT wrote:
I think that features are proposed because user(s) want it, need
it, because it can be useful for other peoples too, because with this
can people solve their problems and/or improve performance and
security of their applications. Not because someone else have
I do not know. Should it be ?
I think that features are proposed because user(s) want it, need it, because
it can be useful for other peoples too, because with this can people solve
their problems and/or improve performance and security of their applications.
Not because someone else have
2011/11/6 Andrus :
> in 8.1+ many char(n) type columns must be in uppercase in database.
> What is best way to force this ?
>
> Should insert and update triggers created for every table or is there better
> way,
> for example by creation domain or adding some attribute to column and
> creating glob
On 11/05/2011 05:36 PM, Andrus wrote:
8.1+ database contains separate schemas for every
company named company1, company2, companyi.
order tables in those schemas contain trigger like for company1:
CREATE OR REPLACE FUNCTION dok_seq_
On Sun, Nov 6, 2011 at 01:17, Tatsuo Ishii wrote:
> It seems web and ssh service on pgfoundry are not available at this
> moment. Anyone knows why?
Hi!
Everything hosted with hub.org has been having serious availability
issues the past week or two (you'll notice the mailinglists have also
been p
On 11/5/2011 4:11 PM, Tom Lane wrote:
Cstdenis writes:
If I understand that you are proposing as
select * from
(select distinct on (user_id) * from stories as s order
by user_id) as foo
order by date_submitted desc limit 10;
No, you always need to sort by *more
in 8.1+ many char(n) type columns must be in uppercase in database.
What is best way to force this ?
Should insert and update triggers created for every table or is there better
way,
for example by creation domain or adding some attribute to column and
creating global trigger?
Andrus
--
Sent
On 11/06/11 8:51 AM, René Fournier wrote:
Just wondering what I can do to squeeze out more performance of my
database application? Here's my configuration:
- Mac mini server
- Core i7 quad-core at 2GHz
- 16GB memory
- Dedicated fast SSD (two SSDs in the server)
- Mac OS X
hubert depesz lubaczewski writes:
> checked lengths of the text/varchar columns in database.
> there are 16 such columns in the table.
> full report of lengths is in
> http://www.depesz.com/various/lengths.report.gz
> it was obtained using:
> select length( "first_text_column" ) as length_1, cou
Just wondering what I can do to squeeze out more performance of my database
application? Here's my configuration:
- Mac mini server
- Core i7 quad-core at 2GHz
- 16GB memory
- Dedicated fast SSD (two SSDs in the server)
- Mac OS X 10.7.2 (*not* using OS X Server)
- PostgreSQL 9.05
- PostGIS 1.5.3
On Fri, Nov 04, 2011 at 09:04:02PM -0400, Tom Lane wrote:
> that. And that they are the only rows that, in addition to the above
> conditions, contain data fields wide enough to require out-of-line
> toasting.
checked lengths of the text/varchar columns in database.
there are 16 such columns in
On 11/06/11 6:07 AM, NTPT wrote:
I use postgresql in my projects since 6.x branch and I am happy with it, but
proposed feature is on my Postgresql wishlist.
Any comments wellcome.
is this based on any existing feature in the SQL specification, or in
other popular database engines?
--
john
TORTUGA SOBRE UN POSTE
Un joven está paseando por una plaza de Caracas y decide tomar un
descanso. Se sienta en un banco y al lado hay un señor de más edad y
naturalmente comienzan a conversar sobre el país, el gobierno y finalmente
de HUGO CHÁVEZ.
El señor le dice al joven: ¿Sabe? HUGO CHÁVE
hubert depesz lubaczewski writes:
> Any chance of getting the fix in patch format so we could test it on
> this system?
http://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=23998fe99c1220ba3a9eefee194e37ec1f14ae07
regards, tom lane
--
Sent via pgsql-general mail
Hi all
I have an idea how to extend postgresql feature set.
I sugest named / preparsed / preplamned query mechanizm where named query is a
simpliest form and preplaned query is the most sofisticated (implementation
wise). Ie to have ability to assign a global and may be persistant NAME (or
22 matches
Mail list logo
