I am using Pgpool II 2.3.3 with Postgresql 8.3.8.
When I use command \l at postgresql client the query is working perfectly.
But if I used the command from pgpool II client which is connected with
postgresql in ssl mode, it gets hang.
Again if I use the command from pgpool II client in non-ssl m
On 08/05/2010 10:33 PM, Tom Lane wrote:
Since you say that --disable-triggers doesn't help, I guess that you're
applying that function not in a trigger but in a CHECK constraint?
That's pretty horrid in itself: CHECK is *not* meant to enforce anything
except local properties of the newly inserted
Rick Yorgason writes:
> In other words, (order_id, product_id) of order_item is a foreign key to
> either reginfo1, reginfo2, or nothing, depending on which product it is.
I think you'll find that few people regard that as good database design.
> The works really well, until I try to use pg_dum
hernan gonzalez writes:
> BTW, I understand that postgresql uses locale semantics in the server code.
> But is this really necessary/appropiate in the client (psql) side?
> Couldnt we stick with C locale here?
As far as that goes, I think we have to turn on that machinery in order
to have gettext
"Boyd, Craig" writes:
> I am trying to pull together some general information about indices
> (indexes?) for a particular table.
> I need the following: Index Name, Table Name, Column Name,
> Unique/Non-Unique, and ordinal position in the index.
> The information_schema.key_column_usage gets me
Hello All,
I am trying to pull together some general information about indices
(indexes?) for a particular table.
I need the following: Index Name, Table Name, Column Name,
Unique/Non-Unique, and ordinal position in the index.
The information_schema.key_column_usage gets me most of the way ther
Bruce Momjian wrote:
> John Gage wrote:
> > Is the documentation available anywhere as a single page text file?
> > This would be enormously helpful for searching using regular
> > expressions in Vim, for example, or excerpting pieces for future
> > reference.
>
> Uh, no, and no one has eve
John Gage wrote:
> Is the documentation available anywhere as a single page text file?
> This would be enormously helpful for searching using regular
> expressions in Vim, for example, or excerpting pieces for future
> reference.
Uh, no, and no one has ever asked for that. There must be so
Wow, you are right, this is bizarre...
And it's not that glibc intends to compute the length in unicode chars,
it actually counts bytes (c plain chars) -as it should- for computing
field widths...
But, for some strange reason, when there is some width calculation involved
it tries so parse the cha
Hey everyone,
I run a website that sells videogames, and different games have
different registration systems, so I have a database design that goes
something like this:
registration_type enum('none', 'regtype1', 'regtype2')
products(product_id, registration_type)
order_item(order_id, produ
This may better-belong in pgsql-sql but since it deals with a function
as opposed to raw SQL syntax I am sticking it here
Consider the following DBMS schema slice
Table "public.post"
Column | Type |
Modifi
LinkedIn
Paulo moraes requested to add you as a connection on LinkedIn:
--
Andrew,
I'd like to add you to my professional network on LinkedIn.
- Paulo
Accept invitation from Paulo moraes
http://www.linkedin.com/e/ATaEtqAFKHyclb4yaP2gMVdFpLR9OB
hernan gonzalez writes:
> Sorry about a error in my previous example (mixed width and precision).
> But the conclusion is the same - it works on bytes:
This example works like that because it's running in C locale always.
Try something like this:
#include
#include
int main () {
char s[]
Hi!
We're having Lightning Talks again at PgCon - scheduled for 5:30pm on
May 20th in Ottawa!
Do you have a talk or idea you'd like to share? Lightning Talks are
one of the most highly attended sessions because they are fast, fun,
and useful (but not always). Slides are not required. If you use
Is the documentation available anywhere as a single page text file?
This would be enormously helpful for searching using regular
expressions in Vim, for example, or excerpting pieces for future
reference.
John
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make c
Thanks very, very much. I got as far as 8.1.4 and did not find 9.15.
May I suggest that the documentation have an index entry under
"serial" for 9.15, which is a major heading whereas 8.1.4 is a minor
heading and has its own index entry?
This is said from the perspective of awe for the doc
On Saturday 8. May 2010 10.11.32 John Gage wrote:
> If I "delete from table", which table contains a serial type field,
> and then insert new rows into the table "excluding the [serial] column
> from the list of columns in the INSERT statement", the numbers in the
> serial column resume where
If I "delete from table", which table contains a serial type field,
and then insert new rows into the table "excluding the [serial] column
from the list of columns in the INSERT statement", the numbers in the
serial column resume where they left off prior to the "delete from
table": 639,
18 matches
Mail list logo
