Greetings,
I'm working with pqlib in asynchronous mode and I have a question about
PQgetResult. I have this situation:
submit a query via PQsendQuery()
flush to the backend with PQflush()
set my read descriptor on the socket and enter a select()
select returns read_ready on the socket, so ca
On Fri, 6 Jul 2001, David Bennett wrote:
> In either model you would:
>
> update master_table set status='OPEN_PENDING_SOMETHING' where status='OPEN'
>
> This would not change, in fact, even in a normalized design you
> wouldn't change the lookup table (parent) key. Perhaps you are
> mi
* Naomi Walker <[EMAIL PROTECTED]> [010706 17:57]:
> If PostgreSQL is run on a system that has a file size limit (2 gig?), where
> might cause us to hit the limit?
PostgreSQL is smart, and breaks the table files up at ~1GB per each,
so it's transparent to you.
You shouldn't have to worry about
If PostgreSQL is run on a system that has a file size limit (2 gig?), where
might cause us to hit the limit?
--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100 ext 242
---(end of broadcast)---
TIP 4: Don't 'kill -9'
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> In 7.2, VACUUM will not require an exclusive lock.
>
> > Care to elaborate on that? How are you going to do it?
>
> Uh, have you not been paying attention to pg-hackers for the
> last two months?
>
> I am assuming here that concurrent VACUUM wil
Tom Lane writes:
> I think you can use the conn->status field; you shouldn't need a new
> flag, just test whether status is CONNECTION_OK or not.
You're right. I was confused by the comment
/* Non-blocking mode only below here */
in the definition of ConnStatusType, thinking that the non-bloc
* Peter Eisentraut <[EMAIL PROTECTED]> wrote:
| > Better user management and policy delegations would be important
| > postgresql to succeed in enterprise environments.
|
| Keeping compatibility is also important.
Well nobody said you can't get both ;-)
| > to all databases, and you can create
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I guess there is sort of a point there. So I'm leaning towards adding a
> "startup complete" flag somewhere in PGconn and simply fix up
> closePGconn().
I think you can use the conn->status field; you shouldn't need a new
flag, just test whether sta
Jan Wieck <[EMAIL PROTECTED]> writes:
> Fire rule actions ON INSERT after original statement (if not INSTEAD).
It seems to me that this change of ordering should apply to
qual_products (ie, original statement with negation of a conditional
INSTEAD rule's condition) as well as to the unvarni
Vitalino writes:
> I have some problem with the Postgres user authentication. A user
> with password was created by me, but when I tried to enter in psql using
> that user I received a fail mesage.
>
> $ psql -W template1 pagano
> Password:
> psql: Peer authentication failed for user 'pagano'
10 matches
Mail list logo
