> I've made a client and a server program in C using socket library.
>
> My goal is to compile the client as a shared object, load it
> dynamically in postgres (in a function), execute that
> postgres function in which this shared library (client) is
> dynamically loaded and connect to the serv
Hi,I've made a client and a server program in C using socket library.The client is in the postgres database server and Server is on some other machine.My goal is to compile the client as a shared object, load it dynamically in postgres (in a function), execute that postgres function in which this s
Hi Tom,
I think I´ve got it...
If you change something in the timezone file that is specified in
postgresq.conf, PG will know this changes automatically? Am I right?
Carlos
> -Mensagem original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] nome de Tom Lane
> Enviada em: terça-fei
On 10/16/06 20:17, Douglas McNaught wrote:
> "Andras Simon" <[EMAIL PROTECTED]> writes:
>
>> I'm trying to create a new tablespace in a directory that postgres
>> owns, but PG says it cannot set permissions on this directory.
>
> ...
>
>> This is on Fedora Core 5 (x86), psql 8.1.4.
>
> SELinux
Yes, it is the 8.0.8 version.
You mean that changes to /etc/localtime should not reflect in the
to_timestamp behavior? Strange, why does to_timestamp behavior changed here
when the /etc/localtime was overlaped?
Well, maybe the PG refresh I´ve done after changing the /etc/localtime did
it (pg_ctl
XimpleWare released Version 1.7 of VTD-XML, the next generation XML
parser that goes beyond DOM and SAX, under GPL. VTD-XML is getting
faster, leaner, more stable and complete with this release. New features
included in this releases are:
* Additional XPath functions support
* Union Expression
*
"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> To discover if it works this way I´ve changed the /etc/localtime to relect
> the following timezone:
Um ... what PG version are you working with? 8.0 and up don't pay
attention to /etc/localtime, because they have their own timezone info.
Hi Tom,
Thank you very much for your explanation!
Let me know if I´ve understood correctly:
If I move the first day DST from Oct 15th to Nov 05th, then the to_timestamp
should show the offset on day Nov 05th and not anymore on Oct 15th, right?
To discover if it works this way I´ve changed the
On 10/17/06, Tom Lane <[EMAIL PROTECTED]> wrote:
To use a nondefault tablespace, you'd want to tweak the policy to allow
postgres to write that directory tree too. I'm afraid I know too little
about selinux to explain exactly what to do though ... need to learn
that someday ...
Me too...
A
On 10/17/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
"Andras Simon" <[EMAIL PROTECTED]> writes:
> I'm trying to create a new tablespace in a directory that postgres
> owns, but PG says it cannot set permissions on this directory.
...
> This is on Fedora Core 5 (x86), psql 8.1.4.
SELinu
"Andras Simon" <[EMAIL PROTECTED]> writes:
> I'm trying to create a new tablespace in a directory that postgres
> owns, but PG says it cannot set permissions on this directory.
> ...
> This is on Fedora Core 5 (x86), psql 8.1.4.
Do you have selinux enabled? The default selinux policy disallows t
> I'm trying to create a new tablespace in a directory that postgres
> owns, but PG says it cannot set permissions on this directory.
>
> [EMAIL PROTECTED] ~]# su - postgres
> -bash-3.1$ mkdir /opt/home/pgdata/mspace/
> -bash-3.1$ psql
> Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
"Andras Simon" <[EMAIL PROTECTED]> writes:
> I'm trying to create a new tablespace in a directory that postgres
> owns, but PG says it cannot set permissions on this directory.
...
> This is on Fedora Core 5 (x86), psql 8.1.4.
SELinux, most likely.
-Doug
---(end of br
I wrote:
> ... I'm not entirely convinced that it really is a POSIX-sanctioned
> notation, either --- the POSIX syntax the zic code knows about is
> different.
Actually, I take that back: it is a subset of the same notation, but
the datetime.c code is misinterpreting the spec!
The POSIX timezone
I'm trying to create a new tablespace in a directory that postgres
owns, but PG says it cannot set permissions on this directory.
[EMAIL PROTECTED] ~]# su - postgres
-bash-3.1$ mkdir /opt/home/pgdata/mspace/
-bash-3.1$ psql
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
Type: \cop
Alexandre Arruda <[EMAIL PROTECTED]> writes:
> But pg_stat_activity joined with pg_locks only give me informations
> about the lock itself.
> Realy, I want a (possible) simple information: Who is locking me ?
You need a self-join to pg_locks to find the matching lock that is held
(not awaited) by
"George Pavlov" <[EMAIL PROTECTED]> writes:
> yes, but int8 is a clearly documented while preceding certain "magic"
> datatype names with underscores is not. i really don't have much of a
> problem with this, but little things like this contribute to people
> coming from other DBMSs developing opin
"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> The problem is related with the to_timestamp function that returns +1 hour
> offset only for the date 15/10/2006. The 15th october is the first day of
> our day light change.
The reason is that it's generating '2006-10-15 00:00:00-03' to start
with,
"Brandon Aiken" <[EMAIL PROTECTED]> writes:
> What about time zones like Tehran (GMT+3:30), Kabul (GMT+4:30), Katmandu
> (GMT+5:45) and other non-cardinal-hour GMT offsets? Is this handled in
> some *documented* way already?
Sure. This has worked since PG 7.2 or so:
regression=# select '12:34:0
Alvaro Herrera escreveu:
Alexandre Arruda wrote:
Hi,
My Database have a lot of locks not granted every moments in a day.
Can I create a view that returns someting like this ?
UserGranted Table Who_is_locking_me PID
--- - - ---
joe f foo
What about time zones like Tehran (GMT+3:30), Kabul (GMT+4:30), Katmandu
(GMT+5:45) and other non-cardinal-hour GMT offsets? Is this handled in
some *documented* way already?
--
Brandon Aiken
CS/IT Systems Engineer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On B
While trying to clean up ParseDateTime so it works reliably with full
timezone names, I found out about a "feature" that so far as I can tell
has never been documented except in comments in datetime.c. The
datetime input code tries to recognize what it calls "POSIX time zones",
which are timezone
Alvaro Herrera wrote:
Hasn't IBM release a pile of it's patents for use (or at least stated
they won't sue) to OSS projects? If so, is this patent covered by that
"amnesty"?
This is useless as a policy, because we have plenty of companies basing
their proprietary code on PostgreSQL, which woul
Madison Kelly wrote:
> Alvaro Herrera wrote:
> >Jochem van Dieten wrote:
> >>Scott Marlowe wrote:
> >>>While all the talk of a hinting system over in hackers and perform is
> >>>good, and I have a few queries that could live with a simple hint system
> >>>pop up now and again, I keep thinking that
Alexandre Arruda wrote:
> Hi,
>
> My Database have a lot of locks not granted every moments in a day.
>
> Can I create a view that returns someting like this ?
>
> User Granted Table Who_is_locking_me PID
> --- - - ---
> joe f foo frank
"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> How can we explain the 01:00:00 hour that the to_date function returns for
> date 15/10/2006?
You haven't fixed your configuration and your machine is considering that
you're in DST.
Lots of machines here in Brazil that weren't updated / fixed by
> On Mon, Oct 16, 2006 at 01:16:34PM -0700, George Pavlov wrote:
> > Hmm, I am not sure I particularly like this behavior or the
> > "ignore it"
> > advice. Suppose someone makes a typo in his/her table
> > definition: meant
> > to create an int4 column but accidentally typed an underscore. You'd
On Mon, Oct 16, 2006 at 01:16:34PM -0700, George Pavlov wrote:
> Hmm, I am not sure I particularly like this behavior or the "ignore it"
> advice. Suppose someone makes a typo in his/her table definition: meant
> to create an int4 column but accidentally typed an underscore. You'd
> expect the stat
Hi,
The problem is related with the to_timestamp function that returns +1 hour
offset only for the date 15/10/2006. The 15th october is the first day of
our day light change.
template1=# select pg_catalog.to_timestamp('15/10/2006','dd/mm/') as
date;
date
20
Alvaro Herrera wrote:
Jochem van Dieten wrote:
Scott Marlowe wrote:
While all the talk of a hinting system over in hackers and perform is
good, and I have a few queries that could live with a simple hint system
pop up now and again, I keep thinking that a query planner that learns
>from its mi
> Yep, the array type is represented internally by prefixings an
> underscore. It's mentioned somewhere in the docs, but you may as well
> ignore it.
Hmm, I am not sure I particularly like this behavior or the "ignore it"
advice. Suppose someone makes a typo in his/her table definition: meant
to c
Hi,
My Database have a lot of locks not granted every moments in a day.
Can I create a view that returns someting like this ?
UserGranted Table Who_is_locking_me PID
--- - - ---
joe f foo frank 1212
jefff foo fra
Jochem van Dieten wrote:
I think you might want to check US Patent 6,763,359 before you
start writing any code.
http://tinyurl.com/yzjdve
- John D. Burger
MITRE
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Jochem van Dieten wrote:
> Scott Marlowe wrote:
> >While all the talk of a hinting system over in hackers and perform is
> >good, and I have a few queries that could live with a simple hint system
> >pop up now and again, I keep thinking that a query planner that learns
> >from its mistakes over ti
Hi,Can two different shared objects be loaded one after the other in the same function so that the second one starts its execution right after the first one finishes.~Harpreet
On Mon, 16 Oct 2006, Oleg Bartunov wrote:
I added some compatibility functions and it worked with new PostgreSQL.
Sorry, I got confused :) I added them to wdb interface
Let me know if you need it
Oleg
On Mon, 16 Oct 2006, Brandon Metcalf wrote:
I'm currently using version 1.9.0 of the old
Scott Marlowe wrote:
While all the talk of a hinting system over in hackers and perform is
good, and I have a few queries that could live with a simple hint system
pop up now and again, I keep thinking that a query planner that learns
from its mistakes over time is far more desirable.
Is it reas
I added some compatibility functions and it worked with new PostgreSQL.
Let me know if you need it
Oleg
On Mon, 16 Oct 2006, Brandon Metcalf wrote:
I'm currently using version 1.9.0 of the old Pg interface with
PostgreSQL 8.0.3. Our code needs to be updated to use DBI/DBD::Pg,
but we need to up
On Mon, Oct 16, 2006 at 12:33:35PM -0700, George Pavlov wrote:
> Is there any special meaning to preceding a datatype (or at least some
> datatypes) in a table or function definition by underscore that is a
> synonym for an array? I can't see it documented anywhere. Below are some
> examples. The o
On Mon, Oct 16, 2006 at 12:15:36PM -0500, Brandon Metcalf wrote:
> I'm currently using version 1.9.0 of the old Pg interface with
> PostgreSQL 8.0.3. Our code needs to be updated to use DBI/DBD::Pg,
> but we need to upgrade PostgreSQL before this is going to happen.
> Does anyone know of any issue
Is there any special meaning to preceding a datatype (or at least some
datatypes) in a table or function definition by underscore that is a
synonym for an array? I can't see it documented anywhere. Below are some
examples. The other question is why "_int4" parses to int[], but "_int"
does not, etc.
am Mon, dem 16.10.2006, um 14:56:27 -0400 mailte Harpreet Dhaliwal folgendes:
> Hi,
> I have a timestamp field in my table and want to set a default value of
> current
> date/time for it.
> What should i enter as its default value? is there any function like now() in
> postgres?
Yes, now() ;-)
Hi Tom,
You are right, I´ve discovered that the to_date was changed to return a
timestamp, the original function is returning the right values.
The to_date I´ve found:
CREATE OR REPLACE FUNCTION PUBLIC.TO_DATE(text, text) RETURNS TIMESTAMP
AS '
BEGIN
RETURN pg_Catalog.TO_TIMESTAMP($1,$2);
END;
'
On Mon, 2006-10-16 at 14:56 -0400, Harpreet Dhaliwal wrote:
> Hi,
> I have a timestamp field in my table and want to set a default value
> of current date/time for it.
> What should i enter as its default value? is there any function like
> now() in postgres?
>
> Thanks,
> ~Harpreet
test=# selec
On Oct 16, 2006, at 1:15 PM, Brandon Metcalf wrote:
Does anyone know of any issues with continuing to use the old Pg
interface with newer versions of PostgreSQL?
it is just a rather thin glue layer on top of the libpq interface, so
it should continue to work just as any libpq app would cont
On Oct 16, 2006, at 1:08 PM, Carlos H. Reimer wrote:
How can we explain the 01:00:00 hour that the to_date function
returns for
date 15/10/2006?
does your timezone change from summer time to winter time (daylight
savings, etc.) on that date?
smime.p7s
Description: S/MIME cryptographic
Harpreet Dhaliwal wrote:
Hi,
I have a timestamp field in my table and want to set a default value of
current date/time for it.
What should i enter as its default value? is there any function like
now() in postgres?
Thanks,
~Harpreet
http://www.postgresql.org/docs/8.1/interactive/functions-d
> can you please provide me the link for the same.
> thanks
The faq is under the documentation link of the PostgreSQL homepage.
http://www.postgresql.org/docs/faq/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
> Just wanted to know how would it make a difference if i use text datatype
> instead of varchar.
Taken from:
http://www.postgresql.org/docs/8.1/interactive/datatype-character.html
"
If character varying is used without length specifier, the type accepts strings
of any size. The
latter is a Pos
Hi,I have a timestamp field in my table and want to set a default value of current date/time for it.What should i enter as its default value? is there any function like now() in postgres?Thanks,~Harpreet
can you please provide me the link for the same.thanksOn 10/16/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Harpreet Dhaliwal wrote:> Hi,> Just wanted to know how would it make a difference if i use text datatype
> instead of varchar.See FAQ item.-- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB
Harpreet Dhaliwal wrote:
> Hi,
> Just wanted to know how would it make a difference if i use text datatype
> instead of varchar.
See FAQ item.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---
Hi,Just wanted to know how would it make a difference if i use text datatype instead of varchar.Thanks,~Harpreet
On Mon, 2006-10-16 at 16:29 +0530, Gandalf wrote:
> I am looking for a *fast* backup/restore tools for Postgres. I've
> found the current used tools pg_dump and pg_restore to be very slow on
> large databases (~30-40GB). Restore takes time in the tune of 6 hrs on
> a Linux, 4 proc, 32 G RAM machine
"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> select to_date('16/10/2006','DD/MM/');
>to_date
> -
> 2006-10-16 00:00:00
> (1 row)
Um... what have you done to to_date()? The standard version returns a
date, not a timestamp:
regression=# select to_date('15/10/20
i changed my connection string as follows keeping newDB in double quotesEXEC SQL CONNECT TO tcp:postgresql://192.168.1.1:5432/"newDB"Unfortunately these doulbe quotes lead to syntax error.Can you tell me what is the right syntax for the same.
ThanksOn 10/13/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"
I'm currently using version 1.9.0 of the old Pg interface with
PostgreSQL 8.0.3. Our code needs to be updated to use DBI/DBD::Pg,
but we need to upgrade PostgreSQL before this is going to happen.
Does anyone know of any issues with continuing to use the old Pg
interface with newer versions of Post
Hi,
I don´t know why the developers build in this way... but let me change a
little bit my question.
I´ve executed tree to_date functions but they give a strange answer for date
16/10/2006 (DD/MM/).
select to_date('16/10/2006','DD/MM/');
to_date
-
2006-10-16 0
"George Pavlov" <[EMAIL PROTECTED]> writes:
> And yes, redirect_stderr = on. I have no definitive way of reproducing
> it, just a vague one: "hit the server with lots of queries".
Hmm. If the messages are less than PIPE_BUF bytes long (4096 bytes on
Linux) then the writes are supposed to be atomi
Adrian Suciu <[EMAIL PROTECTED]> schrieb:
> Hi everybody!
> I ask you for your help on a problem I have.
> I have a postgresql 7.4 running on a dual 4 GB RAM server, but I have some
> VERY memory intense queries, that put processor up to 40%. I see all this
> info in unix "top" command or ps -au
Hi everybody!
I ask you for your help on a problem I have.
I have a postgresql 7.4 running on a dual 4 GB RAM server, but I have
some VERY memory intense queries, that put processor up to 40%. I see
all this info in unix "top" command or ps -aux
Unfortunately they don't show me the query itssel
Martijn van Oosterhout schrieb:
> > create table tt_teste (datfis timestamp without time zone not null
> > CHECK (datfis = trunc(datfis::timestamp without time zone)));
>
> What are you trying to do here? If you only want a date, why not just
> use a date type?
This is an other question ;-)
A
On Mon, Oct 16, 2006 at 12:22:04PM -0200, Carlos H. Reimer wrote:
> Hi,
>
> We´ve a simple insert that is not working. The strange thing is that all
> kind of date are working with the exception of 15/10 (DD/MM) dates.
>
> create table tt_teste (datfis timestamp without time zone not null
> CHEC
Carlos H. Reimer <[EMAIL PROTECTED]> schrieb:
>
> Hi,
>
> WeŽve a simple insert that is not working. The strange thing is that all kind
> of date are working with the exception of 15/10 (DD/MM) dates.
>
> create table tt_teste (datfis timestamp without time zone not null
> CHECK (datfis = tr
Hi,
We´ve a simple
insert that is not working. The strange thing is that all kind of date are
working with the exception of 15/10 (DD/MM) dates.
create table tt_teste (datfis timestamp without
time zone not null CHECK (datfis = trunc(datfis::timestamp without time
zone)));
INSERT INTO tt
On Mon, Oct 16, 2006 at 06:54:31AM -0700, DXScale452 wrote:
> if if i swap the ordering of any of these tables the second in the list
> always fail...
>
> HERE is the syntax of the statements before the fail
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> SELECT value FROM ta
OS: Linux CentOS 4.4PostgreSQL Version: 8.1.4Error: current transaction is aborted, commands ignored until end of transaction blockI have seen this error in your forums... but in those cases... the values being in
On 10/16/06, Alban Hertroys <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> for server side browsing use cursors or a hybrid pl/pgqsl loop. for
> client side, browse fetching relative to the last key:
>
> select * from foo where p > p1 order by p limit k;
This does require some way for the cl
Gandald,have a look athttp://momjian.us/main/writings/pgsql/administration.pdfpage 44ffThere are descriptions how to do database-backups at the speed of raw file system operations.
Harald-- GHUM Harald Massapersuadere et programmareHarald Armin MassaReinsburgstraße 202b70197 Stuttgart0173/9409607-P
I am looking for a *fast* backup/restore tools for Postgres. I've found the current used tools pg_dump and pg_restore to be very slow on large databases (~30-40GB). Restore takes time in the tune of 6 hrs on a Linux, 4 proc, 32 G RAM machine which is not acceptable.
I am using "pg_dump -Fc" to t
On Mon, 16 Oct 2006 11:05:33 +0200
Alban Hertroys <[EMAIL PROTECTED]> wrote:
> This does require some way for the client to keep a single
> transaction open. If this kind of query is performed by a web
> application (as is often the case), the "client" is the server side
> web script engine, and n
On Fri, 13 Oct 2006 16:37:42 +0200
Karsten Hilbert <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 12, 2006 at 04:40:32PM +0200, Ivan Sergio Borgonovo
> wrote:
>
> > Anyway it doesn't solve the problem of having lists that
> > can contain different elements with same parent and maintain
> > ref. integri
Merlin Moncure wrote:
On 10/13/06, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
SELECT * FROM TABLE ORDER BY pk LIMIT 10 OFFSET N;
using offset to walk a table is extremely poor form because of:
* poor performance
* single user mentality
* flat file mentality
databases are lousy at this bec
Jim C. Nasby wrote:
On Thu, Oct 12, 2006 at 05:39:20PM -0500, Scott Marlowe wrote:
It may well be that by first looking at the data collected from problems
queries, the solution for how to adjust the planner becomes more
obvious.
Yeah, that would be useful to have. The problem I see is storing
> Is this new?
> Who ever spent the time to do this, thanks for the effort.
> Having the content organized this way makes it easy to find
> specific reading material.
Are you talking about http://www.postgresql.org/docs/techdocs? If so,
it's been around for quite a whilen ow, but we're still n
75 matches
Mail list logo
